OpenAI Revokes macOS App Certificate After Malicious Axios Supply Chain Compromise
What Happened — OpenAI discovered that a GitHub Actions workflow used to sign its macOS applications inadvertently pulled a malicious version of the Axios JavaScript library on March 31. The compromised library could have been bundled into signed macOS binaries, prompting OpenAI to revoke the affected code‑signing certificate as a precaution.
Why It Matters for TPRM —
- Supply‑chain compromises can affect downstream customers even when no data is exfiltrated.
- Code‑signing certificate revocation signals a loss of trust in the vendor’s build pipeline.
- Third‑party risk programs must verify that vendors enforce strict dependency hygiene and continuous monitoring of their CI/CD environments.
Who Is Affected — AI SaaS providers, enterprise customers using OpenAI macOS desktop apps, and any downstream integrators that redistribute the binaries.
Recommended Actions —
- Review any OpenAI macOS app installations and verify signatures against the newly issued certificate.
- Request evidence of OpenAI’s updated CI/CD security controls (dependency scanning, signed commits, artifact provenance).
- Update internal vendor risk assessments to reflect supply‑chain risk and enforce contractual clauses for secure software development lifecycle (SDLC) practices.
Technical Notes — The attack vector was a compromised third‑party JavaScript dependency (Axios) introduced via a GitHub Actions workflow, not a vulnerability in OpenAI’s code. No user data or internal systems were reported as compromised. Source: The Hacker News