OpenAI Suffers Security Breach From TanStack npm Supply Chain Attack; User Data Unaffected

OpenAI Confirms Security Breach via TanStack npm Supply Chain Attack

OpenAI has recently disclosed a security incident stemming from a sophisticated supply chain attack targeting the TanStack npm package. This breach resulted in the compromise of two employee devices; however, the company assures that no user data, production systems, or intellectual property were affected.

The Mini Shai-Hulud Campaign

On May 11, 2026, a coordinated supply chain attack, dubbed Mini Shai-Hulud, was launched by the cybercriminal group known as TeamPCP. The attackers exploited vulnerabilities within TanStack, a widely utilized open-source JavaScript library, by manipulating its GitHub Actions workflows and Continuous Integration/Continuous Deployment (CI/CD) configurations. This manipulation allowed them to inject malicious code into TanStack’s legitimate release pipeline, resulting in the distribution of compromised package versions that appeared trustworthy to end-users.

Impact on OpenAI

OpenAI’s internal systems inadvertently incorporated the compromised TanStack package before enhanced security measures were implemented. Consequently, two employee workstations were infected. An investigation, conducted with the assistance of a third-party digital forensics and incident response firm, revealed that the attackers engaged in credential-focused exfiltration activities. These activities were confined to a limited subset of internal source code repositories accessible to the affected employees.

The investigation determined that only a minimal amount of credential material was exfiltrated. Importantly, there was no evidence to suggest that customer data, intellectual property, or production code was altered or stolen.

Code-Signing Certificates and Precautionary Measures

Among the compromised repositories were code-signing certificates for OpenAI products across various platforms, including iOS, macOS, Windows, and Android. Although no misuse of these certificates has been detected, OpenAI is proactively rotating all signing certificates as a precautionary measure.

Immediate Response and Containment

Upon detecting the malicious activity, OpenAI implemented several measures to contain the breach:

– Isolated the affected systems and user identities.

– Revoked all active user sessions associated with the compromised accounts.

– Rotated credentials across all impacted repositories.

– Temporarily restricted code-deployment workflows.

– Engaged a third-party incident response firm for comprehensive forensic analysis.

– Collaborated with platform providers to prevent new notarizations using the old certificates.

Action Required for macOS Users

Due to the inclusion of macOS code-signing certificates in the compromised repositories, OpenAI is requiring all macOS users to update their OpenAI applications by June 12, 2026. The affected applications include:

– ChatGPT Desktop (latest version: 1.2026.125)

– Codex App (version 26.506.31421)

– Codex CLI (version 0.130.0)

– Atlas (version 1.2026.119.1)

Post June 12, 2026, macOS security protocols will block any application still signed with the old certificate from launching or receiving updates. Users are advised to download updates exclusively through in-app mechanisms or official OpenAI channels and to avoid third-party download sites, email links, or unsolicited installers claiming to be OpenAI software.

Broader Implications of the Mini Shai-Hulud Campaign

The Mini Shai-Hulud campaign extended beyond OpenAI, compromising hundreds of npm and PyPI packages from various projects, including Mistral AI, UiPath, Guardrails AI, and OpenSearch. The malware specifically targeted developer and cloud credentials, GitHub tokens, npm publish tokens, AWS credentials, Kubernetes secrets, SSH keys, and `.env` files, effectively weaponizing essential tools relied upon by modern DevOps teams.

OpenAI’s Ongoing Security Enhancements

This incident follows a previous compromise involving OpenAI’s developer tools. In response, the company has been implementing hardened CI/CD pipeline controls and package manager configurations to bolster security. OpenAI remains committed to transparency and is taking all necessary steps to safeguard its systems and user data against future threats.