@tanstack/eslint-plugin-start (npm) · Malicious Code
Affects @tanstack/eslint-plugin-startSource GCVE Database
Malicious package : remove @tanstack/eslint-plugin-start and rotate any secrets on hosts that installed it.
Data as of 10 Jul 2026, 10:22 UTC
Malicious package
Published to npm · OSV MAL-2026-3462
What to do
Remove @tanstack/eslint-plugin-start from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@tanstack/eslint-plugin-start | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package @tanstack/eslint-plugin-start versions 0.0.4 and 0.0.7 have been compromised by the TeamPCP threat actor as part of the "Mini Shai-Hulud is back" worm. This malicious package steals credentials from the infected system and attempts to propagate itself to other accessible packages, maintaining persistence on the compromised computer. Systems with this package installed should be considered fully compromised, and all secrets and keys must be rotated from a different, clean system. Removing the package alone does not guarantee removal of all malicious components.
References
- github.com/advisories/GHSA-8hwj-wqhq-3xw2 (opens in a new tab)
- aikido.dev/blog/mini-shai-hulud-is-back-tanstack-compromised (opens in a new tab)
- stepsecurity.io/blog/mini-shai-hulud-is-back-a-self-spreading-supply-chain-attack-hits-the-npm-ecosystem (opens in a new tab)
- socket.dev/blog/tanstack-npm-packages-compromised-mini-shai-hulud-supply-chain-attack (opens in a new tab)
- tanstack.com/blog/npm-supply-chain-compromise-postmortem (opens in a new tab)
- snyk.io/blog/tanstack-npm-packages-compromised/ (opens in a new tab)