On March 31, 2026, attackers published two booby-trapped versions of axios, one of the most widely used building blocks in web development. The versions, 1.14.1 and 0.30.4, were live for about three hours on a package downloaded 100 million times a week. Anyone who installed or built their site during that window may have pulled in remote-control malware.
What is going on
Axios is a small piece of code that developers add to websites and apps to send and receive data. It is distributed through npm, a public library of reusable code components.
A group tracked as Sapphire Sleet spent weeks on social engineering against the project's lead maintainer. They infected his machine with a RAT, short for remote access trojan: malware that lets an attacker control a computer from a distance. With that access they stole his npm publishing credentials.
They then published the two fake axios versions under his name. Those versions quietly pulled in a second package, plain-crypto-js 4.2.1, which installed a RAT that works on Windows, macOS and Linux. Think of it as a trusted supplier's delivery van being used to drop off something nobody ordered.
Who is affected
Only installs that resolved axios 1.14.1 or 0.30.4 during the roughly three-hour window on March 31, 2026 are affected. That mainly means development machines, build servers and automated deployment pipelines that ran an install that day.
Most small business sites do not install npm packages themselves. If an agency or developer rebuilt your site that day, ask them to check. The risk sits on the machines that ran the install, not on visitors to your website.
What to do now
- Check your versions. Look for axios 1.14.1 or 0.30.4 in your project's lock file or installed packages.
- Move off the bad versions. Downgrade or upgrade axios to a clean release, then reinstall.
- Delete the malicious package. Remove the
node_modules/plain-crypto-jsfolder from any affected machine. - Rotate all tokens. Replace npm tokens, API keys, deployment keys and any other secrets that were on the affected machine.
- Harden future installs. In your
.npmrc, setignore-scriptsand a minimum release age so brand-new package versions are not pulled in automatically.
How to check your own site
This attack hit developer machines, but it is a good moment to look at what your live site exposes. The free Website Security Check reports outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. If you want deeper coverage, you can run a full scan, which adds active OWASP Top 10 testing, port and service checks with CVE matching, WordPress and Magento deep scans, and exposed-file and secret checks, on sites whose ownership you have verified.
Source: CISA alert on the axios supply chain compromise, April 2026.
Comments
No comments yet.