![\"\"\/](\"https:\/\/securityaffairs.com\/wp-content\/themes\/security_affairs\/images\/user-icon.svg\"){kind=icon}
Pierluigi Paganini<\/a>\n\t\t\t\t\t\t\t
![\"\"\/](\"https:\/\/securityaffairs.com\/wp-content\/themes\/security_affairs\/images\/clock-icon.svg\"){kind=icon}
May 16, 2026<\/p>\n\t\t\t\t\t\t![\"\"\/](\"https:\/\/www.europesays.com\/ai\/wp-content\/uploads\/2026\/05\/openai.png\")
<\/p>\n
OpenAI said the TanStack supply chain attack compromised two employee devices and exposed credentials from code repositories.<\/p>\n
OpenAI confirmed that the recent TanStack supply chain attack<\/a> compromised two employee devices and exposed credential material stored in internal source code repositories. The incident began after the TeamPCP hacking group<\/a> abused weaknesses in the package publishing process to distribute 84 malicious packages<\/a> tied to the TanStack open source development ecosystem.<\/p>\n Recently, the TeamPCP group launched a new wave of the Mini Shai-Hulud worm<\/a>, compromising legitimate npm packages through hijacked GitHub Actions OIDC tokens. The malware spread through trusted release pipelines and even generated valid SLSA Level 3 attestations, making the malicious packages appear legitimate. Researchers say the worm steals secrets from CI\/CD environments, targets more than 100 credential locations, installs persistence mechanisms in developer tools like VS Code and Claude Code, and spreads automatically to other packages controlled by compromised maintainers. The campaign has already affected packages linked to TanStack, UiPath, DraftLab, and others.<\/p>\n The recent TanStack supply chain attack also impacted OpenAI<\/a> after two employee devices downloaded malicious packages tied to the Mini Shai-Hulud campaign. Attackers stole credential material and secrets from those systems, gaining access to a limited number of internal source code repositories connected to the affected employees.<\/p>\n OpenAI said the security breach had a limited impact and found no evidence that customer data, production systems, or intellectual property were compromised. The company responded by rotating exposed credentials, revoking active sessions, and temporarily tightening restrictions around code deployment workflows.<\/p>\n \u201cWe observed activity consistent with the malware\u2019s publicly described behavior, including unauthorized access and credential-focused exfiltration activity, in a limited subset of internal source code repositories to which the two impacted employees had access.\u201d reads the post<\/a> published by OpenAI. \u201cWe confirmed that only limited credential material was successfully exfiltrated from these code repositories and that no other information or code was impacted.\u201d<\/p>\n The compromised repositories included code-signing certificates used for iOS, macOS, Windows, and Android applications. As a precaution, OpenAI revoked the certificates and began re-signing affected software packages.<\/p>\n \u201cWe are updating our security certificates, which will require all macOS users to update their OpenAI apps to the latest versions.\u201d continues the post. \u201cThis helps prevent any risk, however unlikely, of someone attempting to distribute a fake app that appears to be from OpenAI.\u201d<\/p>\n The company warned that macOS users must update their OpenAI applications before June 12, 2026, or the software may stop receiving updates and could eventually stop functioning correctly.<\/p>\n OpenAI also coordinated with platform providers to block any attempt to abuse the stolen certificates for malicious notarization activities and reviewed previously signed software for signs of tampering.<\/p>\n \u201cWe have also reviewed all notarization of software using our previous certificates to confirm no unexpected software signing has occurred with these keys, and validated that our published software did not have unauthorized modifications.\u201d states OpenAI. \u201cWe have found no evidence of compromise or risk to existing software installations.\u201d<\/p>\n According to the company, the incident occurred during an ongoing migration to hardened configurations introduced after the earlier Axios supply chain attack. The two infected employee devices had not yet received the updated protections that likely would have blocked the malicious package downloads.<\/p>\n \u201cThis incident reflects a broader shift in the threat landscape: attackers are increasingly targeting shared software dependencies and development tooling rather than any single company.\u201d concludes the company.<\/p>\n Follow me on Twitter:\u00a0@securityaffairs<\/a>\u00a0and\u00a0Facebook<\/a>\u00a0and\u00a0Mastodon<\/a><\/p>\n