Axios Compromised: 83 Million Weekly Downloads, a RAT in Your node_modules, and a 3-Hour Window That Could've Gotten You

Every Node.js project you've shipped in the last three years probably has axios in it. I know mine do. So when I saw that axios versions 1.14.1 and 0.30.4 were compromised this morning via hijacked maintainer credentials, my first reaction was to check every lockfile I have.

Here's what happened. The attacker compromised the npm account of maintainer 'jasonsaayman,' pre-staged a malicious dependency called plain-crypto-js, and published two poisoned versions of axios. The dropper was double-obfuscated and deployed platform-specific RATs targeting macOS, Windows, and Linux. The C2 server at sfrclak.com:8000 was already waiting. StepSecurity caught it, and the malicious versions were pulled within about 3 hours. But here's the thing. If your CI pipeline ran npm install during that window, you're potentially compromised. And "clean install" doesn't fix it, the RAT achieves persistence on the host.

This isn't theoretical. 83 million weekly downloads. That's not a niche library. That's practically every production Node.js application. Vercel published dedicated remediation steps the same day, which tells you everything about the blast radius.

What makes this worse is the vibe coding angle. A dedicated r/ClaudeAI thread with 218 upvotes explicitly warned that developers using AI coding assistants are especially vulnerable because the workflow encourages running npm install without reviewing dependency changes. Speed is the whole value proposition. Speed is also how you ship a RAT to production.

What to do right now: check your lockfiles for [redacted] or @0.30.4. Search node_modules for plain-crypto-js. If you find it, rotate every credential on that machine. Pin exact versions in package.json. Add Socket or Snyk to your CI pipeline. This isn't optional hygiene anymore. It's table stakes.

The uncomfortable pattern: this is the second major supply chain attack on AI-adjacent infrastructure today. LiteLLM's PyPI package (3.4 million downloads/day) was also compromised via a Trivy CI/CD pipeline hijack, exposing credentials across an estimated 36% of cloud environments. Two supply chain attacks on core AI developer infrastructure in the same news cycle. Your dependency pipeline isn't a background concern anymore. It's a primary attack surface.