OpenAI has mandated that all macOS users update their software to the latest versions following a supply-chain attack that briefly impacted a popular open-source library in late March. The company stated that while it found no evidence of user data breaches or compromised systems, it is treating its security certificates as compromised and rotating them.
The incident occurred when a North Korean hacking group, identified by Google Threat Intelligence as UNC1069, injected malware into the open-source library Axios. The group reportedly compromised the lead maintainer’s computer and gained control of their accounts, subsequently releasing malicious versions of the software. These tainted versions were live for approximately three hours before being removed.
OpenAI Addresses macOS Security Certificates Post-Attack
OpenAI’s decision to update security certificates and require macOS updates stems from a breach affecting a widely used open-source component. Although the company asserts its own systems and data remained secure, the compromise of the Axios library, which is integrated into OpenAI’s development workflow, necessitates preventative measures. The vulnerability highlights the interconnected nature of software development and the potential for cascading security risks.
The affected library, Axios, is a JavaScript utility used in numerous applications. In this instance, a GitHub workflow employed by OpenAI for signing macOS applications inadvertently executed a malicious version of Axios. While OpenAI’s investigation suggested that the company’s signing certificate was likely not exfiltrated by the malware due to timing and system configurations, the company is taking a precautionary approach.
Supply Chain Attack Details
According to the blog post by OpenAI, the North Korean hacking group’s method involved social engineering to compromise the Axios lead maintainer’s computer. Following this, they gained access to the maintainer’s npm and GitHub accounts, enabling them to insert malicious code into the legitimate software. Jason Saayman, the lead maintainer for Axios, confirmed the duration the malicious code was active before its discovery and removal.
The broader implications of this supply-chain attack are significant. Google Threat Intelligence noted that the compromised Axios library has downstream effects, potentially impacting a vast number of applications that rely on it. Weekly downloads for JavaScript libraries like Axios are in the tens of millions, underscoring the widespread potential exposure. This incident follows other recent compromises of open-source tools, such as Trivy, by a different threat group, UNC6780 (TeamPCP), which resulted in extortion attempts.
OpenAI’s Response and User Impact
OpenAI has emphasized that the malware itself did not directly compromise its signing certificate, which is designed to verify the authenticity of its software. However, to mitigate any potential risk, the company is treating the existing certificate as compromised, leading to its revocation and rotation. This process is essential for maintaining user trust and ensuring the integrity of the software they download.
The company announced that older versions of its macOS applications may cease to function and will no longer be supported after the certificate is fully revoked on May 8. This deadline provides users with a 30-day window to update their software, minimizing disruption. OpenAI has also engaged a third-party digital forensics firm and collaborated with Apple to prevent fraudulent applications from misusing the impacted certificate.
The root cause, as identified by OpenAI, was a misconfiguration within its GitHub workflow. This error has been rectified, and the company is implementing enhanced security protocols. OpenAI stated it would accelerate the certificate revocation date if any malicious activity associated with the compromised certificate is detected.
Moving forward, macOS users are strongly advised to update to the latest versions of OpenAI’s software to ensure continued functionality and security. The company will continue to monitor the situation and will provide further updates as necessary. The next key event will be the full revocation of the certificate on May 8, after which older application versions will become unsupported.