SECURITY ADVISORY — TanStack npm packages
A supply-chain compromise affecting 42 @tanstack/* packages (84 versions total) was published to npm earlier today at approximately 19:20 and 19:26 UTC. Two malicious versions per package.
Status: ACTIVE — packages are deprecated, npm security engaged, publish path being shut down.
Severity: HIGH — payload exfiltrates AWS, GCP, Kubernetes, and Vault credentials, GitHub tokens, .npmrc contents, and SSH keys.
If you installed any @tanstack/* package between 19:20 and 19:30 UTC today, treat the host as potentially compromised:
• Rotate cloud, GitHub, and SSH credentials immediately
• Audit cloud audit logs for the last several hours
• Pin to a prior known-good version and reinstall from a clean lockfile
Detection — the malicious manifest contains:
"optionalDependencies": {
"@tanstack/setup": "github:tanstack/router#79ac49ee..."
}
Any version with this entry is compromised. The payload is delivered via a git-resolved optionalDependency whose prepare script runs router_init.js (~2.3 MB, smuggled into each tarball at the package root).
Unpublish is blocked by npm policy for most affected packages due to existing third-party dependents. All 84 versions are being deprecated with a SECURITY warning, and npm security has been engaged to pull tarballs at the registry level.
Full technical breakdown, complete package and version list, and rolling status updates:
https://t.co/Zy8qG7PA9f
Credit to the security researcher for responsible disclosure.
@Adidotdev In order to understand systems you need to at least understand how code works. Is not one or the other, you need both, and code is fondational
Yes, and that can become expensive quickly. Are you doing only e2e tests? They take time to setup and run, environments isolated from production cost money. I have seen test suites take one hour+ to run. Performance testing can be even more troublesome. Are you going to invest in every feature the same amount of tests/care? Not every feature deserves that level of investing. Can you expand on what your approach would be?
@tzhechev@edandersen Testing is always about tradeoffs. If you have a large and expensive test suite it is going to impact your development flow. It is not reasonable to expect 100% of edge cases to be tested 100% of the time. The test would require 10x more care than the source code.
@FPupusas@TheVolun@ThePrimeagen Nah, reliance on multiple agents turn you away from your codebase in a way other factors would not. If you are ok with it, that's fine too
@mitchellh@thdxr Unless you are in a big corp, does it make sense to use AWS directly? For my hobby projects I get by with a VPS on Digital Ocean or Linode.