We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
OpenAI Blog·May 13·5 min read
Our response to the TanStack npm supply chain attack
TL;DR
A malicious actor compromised TanStack, a popular npm package library (code repository), injecting harmful code into software dependencies that developers download automatically. OpenAI detected the intrusion, revoked affected signing certificates (digital credentials that verify software authenticity), and patched vulnerable systems. macOS users must update OpenAI apps by June 12, 2026 to maintain security.
✦ Why It Matters
Engineers should audit their npm dependencies immediately and implement certificate pinning to detect supply chain compromises before malicious code executes in production.
Key Takeaways
- Audit all npm package dependencies for known vulnerabilities using tools like npm audit.
- Implement certificate pinning to verify software authenticity and detect tampering.
- Establish rapid patching procedures for supply chain incidents affecting critical dependencies.
- Monitor package repositories for anomalous version releases or unexpected maintainer activity.
Full Summary
OpenAI discovered a supply chain attack targeting TanStack, a popular npm package (a reusable code library distributed through Node Package Manager). The attack, named "Mini Shai-Hulud," compromised the package's distribution, potentially affecting any software that depends on it.
OpenAI's response involved identifying which internal systems had pulled the malicious code, isolating those systems from the network, and revoking code-signing certificates—digital credentials that verify software hasn't been tampered with. The company determined that macOS applications required updates by June 12, 2026, to use new valid certificates.
This incident prompted OpenAI to strengthen defenses including enhanced dependency monitoring, stricter certificate rotation policies, and improved detection of anomalous package behavior. The attack highlights how vulnerabilities in shared dependencies can cascade across the software ecosystem.