# openai-confirms-security-breach-via-tanstack-npm-supply-chain-attack: 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.

- **Canonical URL:** https://catalog.anomity.ai/vuln/openai-confirms-security-breach-via-tanstack-npm-supply-chain-attack
- **Aliases:** ti-026
- **Severity:** critical
- **Attack type:** Supply chain compromise, Credential theft
- **Component:** Downstream of @tanstack/* npm packages compromised May (AI agent)
- **Exploited in the wild:** no known exploitation
- **Published:** 2026-05-15
- **Last verified:** 2026-11-01
- **JSON:** https://catalog.anomity.ai/api/entries/vuln/openai-confirms-security-breach-via-tanstack-npm-supply-chain-attack

## Summary

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.

## References

- article: https://www.theregister.com/security/2026/05/15/openai-caught-in-tanstack-npm-supply-chain-chaos-after-employee-devices-compromised/5241019

## Related vulnerabilities

- [mandiant-hijacked-ai-coding-assistant-session-deploys-shai-hulud-across](https://catalog.anomity.ai/vuln/mandiant-hijacked-ai-coding-assistant-session-deploys-shai-hulud-across) — critical
- [anthropic-september-2026-threat-report-fake-claude-code-installers-and](https://catalog.anomity.ai/vuln/anthropic-september-2026-threat-report-fake-claude-code-installers-and) — high
- [keyv-cacheable-npm-worm-writes-auto-run-hooks-into-claude-settings-json](https://catalog.anomity.ai/vuln/keyv-cacheable-npm-worm-writes-auto-run-hooks-into-claude-settings-json) — critical
- [asyncapi-npm-packages-backdoored-with-miasma-malware-framework](https://catalog.anomity.ai/vuln/asyncapi-npm-packages-backdoored-with-miasma-malware-framework) — critical
- [fifteen-jetbrains-marketplace-plugins-harvested-ai-provider-api-keys](https://catalog.anomity.ai/vuln/fifteen-jetbrains-marketplace-plugins-harvested-ai-provider-api-keys) — high
- [trapdoor-cross-ecosystem-supply-chain-attack-poisons-ai-assistant](https://catalog.anomity.ai/vuln/trapdoor-cross-ecosystem-supply-chain-attack-poisons-ai-assistant) — critical

---

Source: Anomity Security Database (https://catalog.anomity.ai/vuln). Detect affected AI tools on developer devices: https://anomity.ai/?utm_source=catalog&utm_medium=vuln-md&utm_campaign=openai-confirms-security-breach-via-tanstack-npm-supply-chain-attack