npm

The Axios npm Supply Chain Attack

Updated 5 Oct 2026 · Incident date 31 Mar 2026

axios 1.14.1 and 0.30.4 on npm added a hidden dependency that installed a remote-control program, published with a stolen maintainer account on 31 March 2026.

The attacker used the stolen npm account of the lead maintainer. npm removed both versions about three hours later.

What happened

Each version added one dependency, plain-crypto-js 4.2.1, which runs a postinstall hook to drop a remote access trojan.

  • Only package.json changed. No axios code imports the dependency.
  • macOS: an AppleScript dropper saves a Mach-O binary to /Library/Caches/com.apple.act.mond and runs it.
  • Windows: a VBScript and PowerShell chain copies powershell.exe to %PROGRAMDATA%\wt.exe and runs a PowerShell RAT. A Run key named MicrosoftUpdate keeps it.
  • Linux: a Python RAT is saved to /tmp/ld.py and started with nohup python3.
  • The dropper deletes setup.js and swaps the manifest, so the folder node_modules/plain-crypto-js is the only sign.

In UTC, 4.2.1 went up on 30 March at 23:59, axios 1.14.1 on 31 March at 00:21 and 0.30.4 at 01:00. npm removed both at about 03:00.

Affected versions

  • axios 1.14.1: malicious, tagged latest, exposed about 3 hours 30 minutes.
  • axios 0.30.4: malicious, tagged legacy, exposed about 2 hours 51 minutes.
  • plain-crypto-js 4.2.1: malicious dependency that runs the dropper.
  • plain-crypto-js 4.2.0: clean decoy.
  • axios 1.14.0 and 0.30.3: clean.
  • A lockfile, cache, Docker layer or build artifact from 31 March can still hold the bad versions.

Indicators of compromise

  • Packages: axios@1.14.1, axios@0.30.4, plain-crypto-js@4.2.1.
  • Folder: node_modules/plain-crypto-js/ (never present in a real axios install).
  • Command server: sfrclak.com, IP 142.11.206.73, port 8000, path /6202033.
  • Related domain on the same IP: callnrwise.com.
  • User-Agent: mozilla/4.0 (compatible; msie 8.0; windows nt 5.1; trident/4.0).
  • macOS file: /Library/Caches/com.apple.act.mond.
  • Windows files: %PROGRAMDATA%\wt.exe, %PROGRAMDATA%\system.bat, %TEMP%\6202033.vbs, %TEMP%\6202033.ps1.
  • Windows registry: HKCU\Software\Microsoft\Windows\CurrentVersion\Run\MicrosoftUpdate.
  • Linux file: /tmp/ld.py.
  • SHA-256 of axios-1.14.1.tgz: 5bb67e88846096f1f8d42a0f0350c9c46260591567612ff9af46f98d1b7571cd.
  • SHA-256 of plain-crypto-js-4.2.1.tgz: 58401c195fe0a6204b42f5f90995ece5fab74ce7c69c67a24c61a057325af668.
  • SHA-256 of the macOS binary: 92ff08773995ebc8d55ec4b8e1a225d0d1e51efa4ef88b8849d0071230c9645a.
  • SHA-256 of the Linux script ld.py: fcb81618bb15edfdedfb638b4c08a2af9cac9ecfa551af135a8402bf980375cf.
  • Attacker email on the hijacked account: ifstap@proton.me. Publisher of plain-crypto-js: nrwise@proton.me.

How to check

Look for the bad version and the plain-crypto-js folder in every project and CI cache. These commands only read files.

npm ls axios plain-crypto-js
ls node_modules/plain-crypto-js
grep -l "plain-crypto-js" package-lock.json yarn.lock pnpm-lock.yaml 2>/dev/null

To find the dropped files, run the line for your system.

ls -l /Library/Caches/com.apple.act.mond   # macOS
ls -l /tmp/ld.py                         # Linux

What to do now

  1. Isolate the machine and rebuild it from a known-good image.
  2. Rotate all credentials the machine or CI job can read, including npm tokens, SSH keys, cloud keys and CI secrets.
  3. Pin axios to 1.14.0 or 0.30.3 with an overrides entry. Remove the bad folder with rm -rf node_modules/plain-crypto-js and reinstall with --ignore-scripts.
  4. Review CI runs of npm install between 31 March 00:21 and 03:25 UTC. Block sfrclak.com and 142.11.206.73.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `axios` 1.14.1. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

axios 1.14.1

A hugely popular web-request library gained a new hidden helper that installs a remote-control program on your machine.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Is this CVE-2026-40175?

No. CVE-2026-40175 is a separate header injection flaw, fixed in 1.15.0 and 0.31.0. It has no link to the malicious releases.

Who is behind the attack?

Huntress reports that Google Threat Intelligence Group linked the attack to UNC1069, a suspected North Korean group.

How widely used is axios?

Endor Labs reports more than 400 million monthly downloads and 174,000 direct dependents.

Sources

  1. web.archive.org/web/20261102142345/https://www.huntress.com/blog/supply-chain-compromise-axios-npm-package
  2. endorlabs.com/learn/npm-axios-compromise
  3. stepsecurity.io/blog/axios-compromised-on-npm-malicious-versions-drop-remote-access-trojan
  4. advisories.gitlab.com/npm/axios/CVE-2026-40175/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library