Dual Supply Chain Attacks in March Compromised Widely Used 'Axios' Library, Spreading Malware

A pair of sophisticated supply chain attacks in late March 2026 compromised popular open-source software tools, including the widely used JavaScript library 'axios', which is downloaded an estimated 100 million times per week. Attackers successfully injected malware into official releases of the software, creating a significant risk of data theft for the tens of thousands of organizations whose applications rely on these components. The most prominent incident, which occurred between Sunday, March 30, and Monday, March 31, involved an unknown attacker hijacking the official account of the lead maintainer for axios on npm, the primary package manager for the JavaScript programming language. The attacker then published malicious versions of the library containing a remote access trojan, according to cybersecurity firm Huntress. Though the tainted versions were quickly identified and removed, any system that automatically downloaded them during that window was potentially compromised. These incidents are a stark reminder that software supply chain risk is now a core business risk. For small and mid-sized companies, the threat is particularly acute. We see many business leaders who assume their software is secure without understanding its underlying components. A compromise like the one affecting axios is not just a technical problem for an IT department; it is a potential backdoor into a company's most sensitive data, including financial records, customer lists, and banking credentials. The malware is specifically designed to steal these assets. In our experience, failing to address these vulnerabilities is no different than leaving the front door of the office unlocked. Proactive assessment and mitigation are essential. This is precisely the kind of threat that our financial risk management services are designed to address, helping clients map their digital dependencies and implement controls to protect their operations and bottom line. To understand and protect against these evolving threats, business leaders can get started by contacting C&S Finance Group LLC at csfinancegroup.com. Security researchers at Step Security analyzed the attack, noting that the malicious versions, labeled “axios@1.14.1” and “axios@0.30.4,” did not contain malicious code within the axios source files themselves. Instead, the attacker added a new, fake software dependency called 'plain-crypto-js'. This dependency's sole purpose was to run a script after installation that deployed the malware, which targeted MacOS, Windows, and Linux operating systems. This method makes the compromise more difficult to detect through a simple review of the main project's code. Feross Aboukhadijeh, CEO of security firm Socket, described the situation as “a live compromise” and “textbook supply chain installer malware” in a post on X, warning that any project pulling the latest version of the tool during the attack window was at risk. The security firm Aikido called it “one of the most impactful npm supply chain attacks on record” due to the library's immense popularity among web developers. This style of attack, where an existing and trusted package is infected, is a well-established but increasingly common strategy. Attackers gain access to a maintainer’s account, often through phishing or by exploiting weak credentials, and then use that legitimate access to distribute malware. The trust that developers place in these established packages becomes the primary vehicle for the attack's propagation. In a similar incident involving the 'eslint-config-prettier' package, an attacker phished the maintainer to steal access and publish multiple unauthorized versions containing malware, according to StepSecurity. Other recent attacks have exploited vulnerabilities in the software development process itself. In a compromise of the 'Nx' developer tool ecosystem, attackers leveraged flaws in a GitHub Actions workflow to steal an npm publishing token. They then used this token to release eight malicious versions of Nx. The malware deployed was designed to harvest a wide range of sensitive information from developer machines, including credentials, SSH keys, npm tokens, and cryptocurrency wallets. It even weaponized locally installed AI command-line tools to perform deep scans of a user's file system. The ultimate goal of these campaigns is typically data exfiltration. The stolen credentials and secrets can be used to launch further attacks, access cloud infrastructure, steal intellectual property, or breach corporate financial systems. This reflects a broader trend of adversaries targeting open-source libraries to maximize their reach. A campaign in July 2025 compromised packages like 'Chalk' and 'Debug', which collectively receive over 2 billion weekly downloads, to deploy backdoors and steal cryptocurrency. The potential damage from such attacks can be catastrophic. The 2017 NotPetya ransomware attack, which was concealed in a malicious update for a popular Ukrainian accounting software, spread globally and caused damages estimated in the billions of dollars, serving as a landmark example of supply chain compromise. In response to the March attacks, security experts have renewed calls for organizations to implement stricter controls over their software dependencies. The incidents highlight the urgent need for tools like Software Bills of Materials (SBOMs), which provide a formal inventory of all components in a piece of software, allowing companies to quickly identify if they are using a compromised version. For now, researchers continue to monitor package repositories for signs of further account takeovers as attackers evolve their methods to exploit the trust inherent in the open-source ecosystem.