Full Breakdown
Axios Supply Chain Attack Compromises Millions of Users
3/31/2026, 11:49:55 AM
Overview of the Attack
Axios, a widely used JavaScript HTTP client with over 300 million weekly downloads, has been compromised in a significant supply chain attack. Two versions of the npm package, specifically axios@1.14.1 and axios@0.30.4, were found to include a malicious dependency, plain-crypto-js@4.2.1, which serves as a remote access trojan (RAT) dropper. This attack was executed using the compromised npm credentials of Axios's primary maintainer, Jason Saayman, allowing the attacker to bypass standard security measures.
Timeline of Events
- March 30, 2026, 05:57 UTC: A clean version of plain-crypto-js@4.2.0 is published.
- March 30, 2026, 23:59 UTC: The malicious version plain-crypto-js@4.2.1 is published.
- March 31, 2026, 00:21 UTC: Axios version 1.14.1 is published, injecting plain-crypto-js@4.2.1.
- March 31, 2026, 01:00 UTC: Axios version 0.30.4 is published with the same malicious dependency.
Mechanism of the Attack
The attacker compromised Saayman's npm account, changing the registered email to a ProtonMail address and publishing the malicious packages directly. The RAT dropper, executed via an obfuscated Node.js script, targets macOS, Windows, and Linux systems, deploying platform-specific payloads. For instance, on macOS, it installs a trojan binary disguised under Apple's cache naming conventions, while on Windows, it uses PowerShell to execute a hidden script. Linux systems receive a Python RAT silently dropped into the /tmp directory.
User Impact and Recommendations
Developers using the compromised Axios versions are advised to take immediate action. They should downgrade to safe versions (axios@1.14.0 or axios@0.30.3), check for specific RAT artifacts, and rotate all credentials. The potential impact of this attack is extensive, affecting frontend frameworks, backend APIs, and CI/CD pipelines.
Criticism & Opposition
Security experts have criticized the npm ecosystem's vulnerability, highlighting the ease with which attackers can exploit maintainer accounts. The attack's sophistication, including the use of a clean decoy version to establish credibility, raises concerns about the effectiveness of current security measures in preventing such incidents.
Official Statements & Responses
Security firms like StepSecurity and Socket have confirmed the attack's details, emphasizing the need for developers to audit their systems and CI/CD pipelines. They recommend implementing stricter security protocols to prevent similar future incidents.
Conflicting Reports & Gaps
While the attack's details have been widely reported, there is no consensus on the identity of the attacker or their motivations. Some analysts suggest that the lack of financial gain indicates the involvement of an advanced persistent threat (APT) actor focused on intelligence gathering rather than monetary theft.
Verbatim Quotes
- “This will go down in history as one of the most successful software supply chain attacks ever,” — Open Source Malware
- “The addition of plain-crypto-js is unambiguous tampering.” — Socket
- “Neither malicious version contains a single line of malicious code inside Axios itself," StepSecurity said.” — StepSecurity
- “If you’ve run npm install in the past several hours, it’s worth checking your dependency files for any of the flagged versions.” — Cyber Kendra
This incident underscores the critical need for enhanced security practices in software development and package management to safeguard against future supply chain attacks.
