CVE-2026-45321
Description
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.
Summary dbcve.org
Attackers exploited a pull_request_target misconfiguration combined with GitHub Actions cache poisoning to extract OIDC tokens from runner memory, allowing them to publish 84 malicious versions across 42 @tanstack/* packages under the legitimate TanStack trusted-publisher identity. This is a sophisticated supply chain compromise chaining three known vulnerability classes.
Mitigation
Immediately revoke and rotate any exposed OIDC tokens/credentials, retract malicious package versions from npm, fix the pull_request_target workflow misconfiguration, implement cache isolation between forks and base repos, and notify all affected users.