Packages / @tanstack/start-server-core / Security
Malicious code in @tanstack/start-server-core (npm)
Compromised versions · @tanstack/start-server-core
- 1.167.36
- 1.167.33
Safe
Every other versionincluding the latest, 1.169.44
npm install @tanstack/start-server-core@1.169.44Not affected
1.114.5 – 1.167.30
375 releases
Affected
1.167.33 – 1.167.36
2 releases
Safe
1.168.0 – 1.169.44
50 releases, latest
Is your project affected?
Paste your package.json, or type the range you declare for @tanstack/start-server-core. It is read in your browser and sent nowhere.
What happens
If one of these versions was installed
- Treat the machines and CI runners that installed it as compromised.
- Rotate the npm, GitHub and cloud tokens they could reach.
- Reinstall from a lockfile that pins a version outside the list.
-= Per source details. Do not edit below this line.=-
Source: ghsa-malware (7db0631bb410a51551790c0b55b574d53aea5d7a677439e6f3cf877503317658)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Source: google-open-source-security (5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5)
This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.
The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.