🎯Basically, OpenAI had to cancel its app certificate because a hacker used it to spread malware.
What Happened
On March 31, OpenAI discovered that a GitHub Actions workflow used to sign its macOS applications inadvertently downloaded a malicious version of the Axios library. This incident was linked to a supply chain attack orchestrated by the North Korean hacking group UNC1069. OpenAI assured users that no data was compromised, but they took precautionary measures by revoking the signing certificate.
Who's Behind It
The attack was attributed to UNC1069, which hijacked the npm account of the Axios package maintainer. They pushed poisoned versions of Axios that contained a malicious dependency named plain-crypto-js, which deployed a backdoor called WAVESHAPER.V2 across various operating systems, including Windows, macOS, and Linux.
Tactics & Techniques
The malicious payload was executed within the GitHub Actions workflow, which had access to the signing certificate for OpenAI's apps. OpenAI stated that the timing and execution sequence of the attack likely prevented the malicious payload from successfully exfiltrating the certificate. However, they are treating it as compromised and have taken steps to rotate it.
Defensive Measures
OpenAI will stop supporting older versions of its macOS apps starting May 8, 2026, as these versions will be blocked by macOS security protections. Users are encouraged to update to the newer versions of the apps, which are signed with a new certificate. OpenAI is also collaborating with Apple to ensure that software signed with the compromised certificate cannot be notarized.
Industry Impact
This incident is part of a larger trend of supply chain attacks targeting popular open-source libraries. Alongside the Axios incident, another attack on Trivy, a vulnerability scanner, has caused ripple effects across various ecosystems. These attacks highlight the vulnerabilities in the software supply chain and the need for enhanced security measures in development practices.
What to Watch
As cybercriminals evolve their tactics, organizations must adapt by implementing stricter verification processes for dependencies and ensuring that their CI/CD pipelines are secure. The recent incidents serve as a reminder of the inherent trust developers place in open-source software and the need for explicit verification at every layer of the software stack.
🔒 Pro insight: This incident underscores the critical need for enhanced security practices in CI/CD pipelines to mitigate supply chain vulnerabilities.
