this post was submitted on 12 May 2026
80 points (100.0% liked)
Programming
26909 readers
427 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
it was coming from the original package publisher. tanstack was cache poisoning via pr, so no account credentials were stolen but it was published as a normal update
https://tanstack.com/blog/npm-supply-chain-compromise-postmortem
and then other packages like mistral were affected because they depend on tanstack so those were direct credential hijacks?
probably not, I haven't seen any other post mortems but the tanstack ones were only up for 20 minutes so really low chance. I wouldn't be surprised if they were all a similar approach and that's why they all happened at the same time