massive campaign for 170+ packages and 400+ malicious versions published. what we saw that not a single maintainer account compromised. tanStack and Mistral AI these are the names that stand out.
massive campaign for 170+ packages and 400+ malicious versions published. what we saw that not a single maintainer account compromised. tanStack and Mistral AI these are the names that stand out.
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