Threat intelligence · CVEs & news
Published: 05/12/2026 · Modified: 10/26/2026
On 2026-05-11, between approximately 19:20 and 19:26 UTC, 84 malicious versions across 42 @tanstack/* packages were published to the npm registry. The publishes were authenticated via the legitimate GitHub Actions OIDC trusted-publisher binding for TanStack/router, but the publish workflow itself was not modified. The attacker chained three known vulnerability classes — a pull_request_target "Pwn Request" misconfiguration, GitHub Actions cache poisoning across the fork↔base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — to publish credential-stealing malware under a trusted identity. Each affected package received exactly two malicious versions, published a few minutes apart.
Requires: network access, victim action · Does not require: authentication, special target conditions
Not enough data to detail.
Not enough data to detail.
Does not require: authentication, special target conditions.
Not enough data to detail.
Confidentiality: highIntegrity: highAvailability: high
Also affects components beyond the vulnerable one.
The “Requires/Does not require” line and the confidentiality, integrity and availability impact come from the official CVSS vector. Method, applicability and mitigation are an automatic summary of the NVD description, public exploitation sources (Metasploit, Nuclei, Exploit-DB) and the CVE record via CIRCL (advisories and fixed version), linked under “References and technical detail”. Community reports come from CIRCL sightings and are unverified.