MalwarePublished 29 Apr 2026

tanstack (npm) · Malicious Code

Affects tanstackSource GCVE Database

Malicious package : remove tanstack and rotate any secrets on hosts that installed it.

Data as of 27 Oct 2026, 00:33 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-3190

What to do

Remove tanstack 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
npmtanstack	Affected 2.0.4 – 2.0.7 4 affected builds	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' versions 2.0.4 through 2.0.7 contain malicious code. Installation or execution of this package can lead to full compromise of the affected computer, potentially exposing all stored secrets and keys. Immediate removal of the package and rotation of all secrets from a different, uncompromised machine is strongly recommended.

Impact

Systems with the affected versions of the 'tanstack' package installed are at risk of full compromise. Attackers may gain complete control over the system, leading to potential theft or misuse of secrets, keys, and sensitive data. The compromise undermines system integrity and confidentiality, requiring urgent remediation.

Defensive guidance

Remove the affected 'tanstack' package versions (2.0.4 to 2.0.7) immediately. Rotate all secrets and keys stored on the compromised system from a separate, trusted machine. Due to the likelihood of persistent compromise, assume the system is fully controlled by an attacker and consider rebuilding or thoroughly cleaning the environment.

Summary

The 'tanstack' npm package versions 2.0.4, 2.0.5, 2.0.6, and 2.0.7 have been identified as containing malicious code. According to sources including Amazon Inspector and the GitHub Security Advisory for malware, any system with this package installed or running should be considered fully compromised. The malicious code may grant an external attacker full control over the system, risking exposure of all stored secrets and keys. Removing the package alone does not guarantee eradication of all malicious artifacts or backdoors introduced by the compromise.

References

github.com/advisories/GHSA-5w4c-85pv-cwhv (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 00:33 UTC

Technical details

References

Community reviews