PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
OpenAI’s macOS app-signing workflow executed malicious code from a compromised Axios npm package on March 31, 2026. OpenAI said it found no evidence that customer data, intellectual property, released software, or its signing certificate was actually compromised. It nevertheless rotated the certificate, issued replacement-signed builds, and required users of older macOS versions to update by May 8, 2026.
This was a serious software-supply-chain exposure—not a confirmed breach of OpenAI accounts or customer data. The incident was linked by security researchers to a North Korea-nexus threat actor, although that attribution should be treated as reported intelligence rather than independently proven state responsibility.
The short version
- A malicious release of the widely used Axios JavaScript package was published on March 31, 2026.
- OpenAI’s macOS signing workflow installed and executed
[email protected]. - The workflow had access to macOS code-signing and Apple notarization material for products including ChatGPT Desktop, Codex App, Codex CLI, and Atlas.
- OpenAI said it found no evidence of user-data access, altered released software, stolen intellectual property, or misuse of its certificate.
- OpenAI rotated the certificate as a precaution and told macOS users to install replacement-signed versions.
The most accurate description is that malicious third-party code ran inside a privileged OpenAI build workflow. That is different from saying that ChatGPT users were hacked or that OpenAI distributed malware.
OpenAI’s incident account is the primary source for the company’s findings and remediation.
#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
What is Axios, and why did its compromise matter?
Axios is an open-source JavaScript HTTP client distributed through npm, the package registry commonly used by Node.js projects. It is used directly by some applications and indirectly as a transitive dependency by many others. Security reporting described its reach as ranging from tens of millions to more than 100 million weekly downloads, depending on the measurement and date.
The risk was not simply that developers might receive a buggy HTTP library. npm packages can run lifecycle scripts during installation, including postinstall hooks. In a developer laptop or CI/CD runner, those scripts may inherit environment variables, repository tokens, cloud credentials, or release-signing material.
That creates a dangerous chain:
compromised maintainer account → poisoned npm release → CI dependency installation → malicious lifecycle code → exposure of signing workflow
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesDownloading a package does not automatically prove that a host was compromised. The relevant questions are whether the poisoned version was resolved, installed, executed, able to reach its command-and-control infrastructure, and able to access or exfiltrate useful credentials.
What happened on March 31, 2026?
According to security reporting, attackers used social engineering to compromise an Axios maintainer’s npm account. Two malicious releases were reported:
The releases reportedly introduced an additional dependency and used an installation hook to deploy a cross-platform remote-access payload. They were available for only a limited period—reported as roughly three hours—before removal.
That window did not mean every Axios user was compromised. Exposure depended on whether an environment installed one of the poisoned versions while it was available and whether the malicious code executed successfully. See the incident coverage from SecurityWeek, Zscaler, and the Cloud Security Alliance.
Rank #2
- POWERFUL SECURITY KEY: The YubiKey 5C NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5C NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5C NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
How did the attack reach OpenAI?
OpenAI said a GitHub Actions workflow used to sign its macOS applications downloaded and executed [email protected] on March 31.
That workflow had access to:
- a macOS code-signing certificate; and
- Apple notarization material.
The credentials were used in the release process for ChatGPT Desktop, Codex App, Codex CLI, and Atlas. This made the incident significant even though the compromised package was a general-purpose developer tool: it ran in a workflow close to credentials capable of establishing software authenticity.
Secondary technical analysis reported that the workflow used a floating reference rather than a specific commit hash and did not configure a minimumReleaseAge delay for newly published packages. A floating reference can resolve to whatever version is current when a job runs. Without a cooling-off period, a newly published package may be trusted immediately, before security teams or the wider ecosystem have had time to identify suspicious behavior. These details come from secondary technical reporting and should not be treated as a complete statement of OpenAI’s current controls.
Was OpenAI hacked?
Yes, in the narrow infrastructure sense: malicious code from a third-party dependency executed in an OpenAI signing workflow.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →No, based on OpenAI’s disclosure, this was not a confirmed customer-data or released-software breach. OpenAI said its investigation found no evidence that:
- user data was accessed;
- OpenAI systems or intellectual property were compromised;
- published software was altered without authorization;
- the signing certificate was successfully exfiltrated; or
- malware was signed as OpenAI or the old notarization material was misused.
Those findings do not make the event harmless. They mean the observed evidence did not establish the worst-case outcome. OpenAI treated the certificate as potentially compromised anyway, which is the prudent response when a privileged signing environment has executed untrusted code.
Why was the signing certificate important?
A code-signing certificate helps macOS identify software as coming from a particular developer. If an attacker had successfully obtained and misused OpenAI’s signing credentials, the attacker could potentially sign malicious software so that it appeared to originate from OpenAI.
Rank #3
- POWERFUL SECURITY KEY: The YubiKey 5 NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
That could have supported fake ChatGPT, Codex, or Atlas installers and made social-engineering attacks more convincing. It would not automatically guarantee that every Mac would install or trust the software, and OpenAI said it saw no evidence that such misuse occurred.
This distinction matters:
- Certificate exposure risk: the workflow had access to valuable signing material while malicious code ran.
- Certificate theft: OpenAI said the material was likely not successfully exfiltrated.
- Certificate misuse: OpenAI reported no evidence that malware was signed or distributed using it.
What OpenAI did in response
OpenAI said it:
- Engaged a third-party digital forensics and incident-response firm.
- Rotated its macOS code-signing certificate.
- Published new builds of affected macOS products using the replacement certificate.
- Worked with Apple to prevent new notarization using the previous certificate.
- Reviewed notarization events associated with the old certificate.
- Validated that published software had not been unauthorizedly modified.
- Required users to update older macOS applications.
Certificate rotation can create a practical burden for users on old versions, but it is preferable to leaving potentially exposed credentials active. Revocation and rotation also do not necessarily remove software that is already installed; they are part of a broader trust, update, and release-response process.
Which users and products were affected?
OpenAI said the remediation applied to its macOS applications only. It did not apply to the company’s web applications, iOS apps, Android apps, Linux apps, or Windows apps. OpenAI also said users did not need to change their passwords or API keys because of this incident.
The company listed these earliest releases signed with the replacement certificate:
| Product | Earliest replacement-certificate version |
|---|---|
| ChatGPT Desktop | 1.2026.051 |
| Codex App | 26.406.40811 |
| Codex CLI | 0.119.0 |
| Atlas | 1.2026.84.2 |
OpenAI said that, effective May 8, 2026, older macOS application versions would no longer receive updates or support and might not remain functional. That should not be generalized to non-macOS products.
What macOS users should do
- Update ChatGPT Desktop, Codex App, Codex CLI, or Atlas through the application’s built-in updater or an official OpenAI download page.
- Check that the installed version meets the replacement-certificate version listed above.
- Do not use installers received through email, advertisements, social-media posts, file-sharing services, or third-party download portals.
- If you use only OpenAI through the web, iOS, Android, Linux, or Windows, the macOS certificate remediation does not apply according to OpenAI.
- Password and API-key changes are not required solely because of this incident, according to OpenAI.
How certain is the North Korea attribution?
Security researchers linked the campaign to a North Korea-nexus actor identified in some reporting as UNC1069. Microsoft-related reporting has used a different designation, Sapphire Sleet. Threat-intelligence naming systems can overlap or classify related activity differently.
The careful wording is therefore “North Korea-linked,” “North Korea-nexus,” or “attributed by security researchers.” The direct evidence establishes the malicious npm releases and OpenAI workflow exposure. The broader state attribution comes from external security analysis and should not be presented as independently proven fact.
Rank #4
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
What software teams should learn
1. Pin dependencies and review lockfiles
Use exact package versions and lockfiles with integrity data where practical. Review lockfile changes as code changes rather than allowing silent dependency resolution.
Pinning is not a complete defense: a package can be compromised before a version is pinned, and a maintainer-account compromise can affect a future update. For GitHub Actions and similar automation, pin third-party actions to a specific commit SHA rather than relying only on a mutable tag.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →2. Add a package cooling-off period
A minimum release-age policy delays adoption of newly published packages. This does not guarantee safety, but it gives scanners, maintainers, and the security community time to identify suspicious releases.
3. Treat lifecycle scripts as executable code
Installation hooks can run before application tests or review steps. Disable lifecycle scripts where they are not required, or install dependencies in an isolated stage with minimal permissions.
4. Separate dependency installation from signing
The most important architectural lesson is privilege separation. A job that installs untrusted packages should not simultaneously hold production signing keys or notarization credentials.
A safer sequence is to complete dependency installation and testing in an isolated environment, produce a verified artifact, and perform signing in a hardened job that receives only the artifact and short-lived, least-privilege credentials.
Recommended Free Tools
5. Restrict secrets and network access
- Inject signing secrets only after untrusted build steps finish.
- Use short-lived credentials and least-privilege CI tokens.
- Restrict outbound network access from build jobs where feasible.
- Monitor package publication, maintainer-account, and dependency changes.
- Log code-signing and notarization activity.
- Maintain and test an emergency certificate-rotation and update process.
Network restrictions and lockfiles have trade-offs. Package installation, telemetry, and release tools may require outbound access, and a stale or bypassed lockfile can undermine dependency controls. These measures should be layered rather than treated as a single fix.
Best Value
- Security Key : Protect your online accounts against unauthorized access by using FIDO2 and U2F authentication with T110. It's the world's most protective security key that works with windows, Mac OS, Linux as well as Chrome, Firefox, Edge and many other major browsers.
- Certified with the new FIDO2 standard, T110 provides the benefit of fast login and strong protection against phishing, account takeover as well as many other online attactks.
- Works with : Bank of America, Github, Google, Microsoft, DUO, Twitter, Facebook, Dropbox, Apple, ebay, BINANCE, mor and more.
- Fits USB-A port : Insert the T110 security key into the USB-A port of each service and log in conveniently with one touch
- For the driver download and user guide, please visit TrustKey Solutions Home support page.
How companies can investigate possible exposure
Teams that installed Axios during the relevant window should distinguish the following events:
- The package was resolved.
- The package was installed.
- An installation hook or other malicious code executed.
- The payload obtained network access.
- It accessed environment variables, tokens, certificates, or other secrets.
- Those secrets were exfiltrated or misused.
- A release artifact was modified or signed.
Review lockfiles, package-manager logs, CI job logs, runner images, outbound network telemetry, secret-access events, artifact hashes, code-signing records, and notarization records. Rotate credentials if the relevant job had access to them, even when forensic evidence is inconclusive. “No evidence of misuse” is not the same as proof that misuse was impossible.
Tools that may help prevent similar incidents
Organizations evaluating controls may consider several categories of products, but no product should be assumed to have prevented this specific exposure without documented evidence.
Free tools Windows power users keep installed
One-click scans. No signup required.
- GitHub Advanced Security: dependency review, secret scanning, code scanning, and GitHub Actions integration.
- Socket: analysis of open-source package behavior, install scripts, dependency changes, and suspicious npm activity.
- Snyk Open Source: software-composition analysis, dependency policy, vulnerability, and license monitoring.
- JFrog Xray: artifact and dependency scanning across repositories and delivery pipelines.
- Wiz: cloud-security and workload-exposure analysis after a dependency executes in cloud infrastructure.
- npm Enterprise: controlled package-management workflows and private registry capabilities.
These tools address different layers. Package analysis does not replace signing-key isolation; cloud-security posture management does not replace npm controls; and a private registry does not automatically make upstream packages safe.
Bottom line
The Axios incident was a serious near-miss involving a privileged OpenAI macOS signing workflow. Malicious npm code executed where signing and notarization material was available, creating a theoretical path to counterfeit OpenAI software. But OpenAI reported no evidence that user data, customer accounts, intellectual property, released applications, or its certificate were actually compromised.
Mac users should use official update channels and meet the replacement-certificate versions. For engineering teams, the central lesson is architectural: do not let ordinary dependency installation run beside the credentials that can establish trust in production software.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
