On March 31, 2026, someone hijacked a software library that gets downloaded 100 million times per week and injected a hidden backdoor into it. The compromised versions were live for about two hours before anyone caught it.

Two hours. That’s all it took.

If your business runs a website, a mobile app, a customer portal, or any internal tool built with JavaScript — and most businesses do — there’s a reasonable chance your systems pulled that update automatically during that window. The malicious code would have executed silently, without anyone clicking anything, without any warning, without any alert.

This isn’t a phishing email someone should have spotted. This is a supply chain attack — and it’s becoming the most significant cybersecurity threat that most business owners have never heard of.

What Actually Happened

Axios is a software library that developers use to make web requests. If you’ve ever filled out a form on a website, loaded data from a server, or used an app that talks to the internet — Axios was probably involved somewhere. Over 174,000 other software packages depend on it.

An attacker gained access to the credentials of the lead Axios maintainer on npm, the world’s largest software package registry. Using those stolen credentials, the attacker published two backdoored versions of Axios — one on the current release and one on the legacy release — within 39 minutes of each other. This ensured maximum reach across both old and new projects.

The backdoored versions included a hidden dependency called “plain-crypto-js” that had been staged 18 hours earlier as a clean package to avoid suspicion. When any developer or automated build system ran a standard install command, the malicious code executed automatically — no user interaction required.

Within 1.1 seconds of installation, the malware connected to a command-and-control server and began stealing credentials: cloud access keys, database passwords, API tokens, and anything else stored on the system. It then installed a Remote Access Trojan that gave the attacker persistent access to the compromised machine. The malware was built for Windows, macOS, and Linux simultaneously — three parallel versions sharing an identical command structure.

After executing, the malware deleted itself to avoid forensic detection.

Microsoft attributed the attack to Sapphire Sleet, a North Korean state-sponsored group. Google’s Threat Intelligence team independently attributed it to a related North Korean actor. This was not a teenager in a basement. This was a nation-state operation with significant resources and planning.

Why This Matters to Your Business

You don’t need to understand npm or JavaScript to understand the risk. Here’s the business translation:

Your company uses software. That software was built with components made by other people. Those components were built with components made by other people. The Axios attack targeted a component so foundational that it sits inside hundreds of thousands of applications — many of which your business may use or depend on without knowing it.

This is vendor risk at a level most companies have never considered. When you evaluate a software vendor, you probably ask about their security practices. But do you ask about the security of their dependencies? Do you know what open-source libraries are inside the tools you pay for? Do your vendors know?

The SANS Institute put it simply: “The attack surface is your vendor’s vendor’s vendor.”

And this isn’t isolated. Between March 19 and March 31, the same campaign compromised four other widely used open-source tools: the Trivy vulnerability scanner (ironically, a security tool), the KICS infrastructure scanner, the LiteLLM AI library, and the Telnyx communications library. The LiteLLM compromise led directly to a separate breach at Mercor, a $10 billion AI startup that works with OpenAI and Anthropic, where attackers claim to have exfiltrated 4 terabytes of data.

What This Means for Your Vendor Relationships

Most businesses evaluate vendors based on what they deliver, not what they’re built on. The Axios incident changes that calculation.

Ask your software vendors about their dependency management. Do they pin exact versions of their dependencies, or do they auto-update? Do they audit their supply chain? Do they have a Software Bill of Materials (SBOM) that lists every component in their product?

Ask your IT provider about your exposure. If your business runs any web applications, internal tools, or customer-facing portals, ask your IT team whether any of them use Axios — and whether they were running during the two-hour window on March 31. If your IT provider can’t answer that question quickly, that’s a signal worth paying attention to.

Understand that traditional security doesn’t catch this. Firewalls, antivirus, and endpoint protection didn’t detect the Axios attack because the malicious code came through a trusted channel. The software update system did exactly what it was designed to do — it updated. The problem was that the update itself was compromised.

What You Can Do Right Now

You don’t need to become a software security expert. But you do need to ask better questions of the people and companies your business depends on.

Start by understanding your own exposure. What software does your business run? Who built it? What happens when it updates? If a component inside one of your tools was compromised, how would you know — and how quickly could you respond?

These are the questions that separate businesses that recover from supply chain incidents from those that discover the damage months later.

Take the 2-Minute Cybersecurity Assessment

Sources

Socket Security: “Supply Chain Attack on Axios Pulls Malicious Dependency” (March 31, 2026) — First to detect compromised packages within 6 minutes of publication
Microsoft Security Blog: “Mitigating the Axios npm supply chain compromise” (April 1, 2026) — Attributed attack to Sapphire Sleet, North Korean state actor
Elastic Security Labs: “Inside the Axios supply chain compromise” (April 1, 2026) — Technical analysis of cross-platform RAT architecture
SANS Institute: “Axios NPM Supply Chain Compromise” (March 31, 2026) — Industry analysis and remediation guidance
Snyk: “Axios npm Package Compromised: Supply Chain Attack” (March 31, 2026) — 100M weekly downloads, 2-hour exposure window
The Hacker News: “Axios Supply Chain Attack Pushes Cross-Platform RAT” (March 31, 2026) — Attack staged 18 hours in advance, both release branches hit in 39 minutes
Huntress: “Supply Chain Compromise of axios npm Package” (March 31, 2026) — Timeline reconstruction, C2 analysis
Fortune: “Mercor, a $10 billion AI startup, confirms major security incident” (April 2, 2026) — Downstream impact of related LiteLLM supply chain attack
SOCRadar: “Axios npm Hijack 2026: Everything You Need to Know” (April 1, 2026) — Google Threat Intelligence attributed to UNC1069, North Korean actor