Our response to the Axios developer tool compromise

OpenAI spent part of this week cleaning up after a supply chain scare that started nowhere near its own code. Axios, a widely used JavaScript library for making HTTP requests, turned out to be the entry point for a compromise that rippled outward into tools built on top of it — including some of the developer infrastructure OpenAI relies on for building and signing its macOS apps.

The company's response was blunt and mechanical rather than dramatic: rotate the code signing certificates used for its Mac applications, push updated builds signed with the new keys, and audit the build pipeline for anything that looked tampered with. Code signing certificates are the digital signature that tells your Mac an app really came from who it claims to, so swapping them out is the equivalent of changing every lock in the building the moment you suspect someone copied a key.

OpenAI says its investigation found no evidence that user data was accessed or exfiltrated, and no indication that the compromised certificates were used to distribute malicious versions of its apps. That's the best-case outcome in this kind of incident — the blast radius stayed contained to infrastructure rather than reaching actual people's accounts or files.

What makes this notable isn't OpenAI's specific exposure, which appears to have been limited. It's the reminder that a company can write airtight code and still get dragged into an incident because of a dependency three or four layers down in its toolchain. Axios itself is unglamorous plumbing — the kind of library thousands of projects import without a second thought — and that ubiquity is exactly why attackers target it. Compromise one popular package and you get a foothold into who knows how many downstream systems, some of them belonging to companies with far more sensitive stuff to protect than a request client.

OpenAI's fix here was fast and procedural, which is the right instinct. Rotate the keys, ship the update, tell people what happened. The harder problem, the one this incident doesn't really solve, is that the entire industry keeps building critical software on a foundation of open source packages nobody is paying to audit properly.