OpenAI Confirms Security Breach via TanStack npm Supply Chain Attack
OpenAI Confirms Security Breach via TanStack npm Supply Chain Attack is a critical-severity supply chain compromise issue in Downstream of @tanstack/* npm packages compromised May, an AI agent. Affected: Downstream of @tanstack/* npm packages compromised May 11.
Is Downstream of @tanstack/* npm packages compromised May running on your developers' machines? Anomity finds every device with this AI agent installed, shows the version, and can block it by policy. Detect this across your developers' devices with Anomity →
Key facts
- ID
openai-confirms-security-breach-via-tanstack-npm-supply-chain-attack- Severity
- critical
- Attack type
- Supply chain compromise, Credential theft
- Component
- Downstream of @tanstack/* npm packages compromised May · AI agent
- Known exploited
- No known exploitation
- Published
- Last verified
What is this vulnerability?
OpenAI confirmed that two employee workstations were silently compromised in the May 11 TanStack supply chain attack, exposing internal CI tokens and a subset of developer credentials. The company says no customer data was accessed, the compromised tokens have been rotated, and the affected machines re-imaged. The disclosure highlights that even AI vendors with mature security programs are downstream of the same npm supply-chain risks that hit their customers.
Affected versions
| Affected | Fixed in |
|---|---|
Downstream of @tanstack/* npm packages compromised May 11 | No fixed version listed |
Am I affected by this vulnerability?
You are affected if you run Downstream of @tanstack/* npm packages compromised May 11.
How do I fix it?
Confirm none of the May 11 backdoored @tanstack/* versions are pinned in your lockfiles. Rotate any tokens passed through CI runners that ran installs in that window. Adopt vendor-signed-attestation enforcement in npm install where possible.
How do I find every machine running Downstream of @tanstack/* npm packages compromised May?
Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run Downstream of @tanstack/* npm packages compromised May and which version, then enforce a policy on it.