North Korea Backdoored Axios. 100 Million Weekly Downloads, 3 Hours of Exposure, and a RAT on Every Platform.

Every Node.js project you've ever touched probably depends on Axios. On March 31, a compromised npm maintainer account pushed backdoored versions 1.14.1 and 0.30.4 that silently installed a cross-platform remote access trojan on macOS, Windows, and Linux.

The attack chain was clean. The malicious versions added plain-crypto-js as a dependency, a fake package whose postinstall hook dropped platform-specific RAT implants. No jailbreak. No user interaction required. Just npm install and you're owned. Microsoft Threat Intelligence attributed the attack to North Korean state actor Sapphire Sleet. Google independently attributed it to UNC1069. The malicious packages were live for 2 to 3 hours before npm pulled them. Safe versions are 1.14.0 and 0.30.3.

I keep thinking about the timing. This lands one day after the LiteLLM supply chain attack that hit Mercor for 4TB. Two major npm/PyPI supply chain compromises in the same week targeting AI-adjacent tooling. That's not coincidence. That's a campaign. The Fireship video covering the attack hit 564K views in 24 hours, so awareness is high. But awareness isn't defense.

GitHub's response was fast and material. They announced a new dependencies: section in workflow YAML that locks all direct and transitive dependencies with commit SHAs, expanded OIDC trusted publishing across npm/PyPI/NuGet/RubyGems/Crates, and deprecated TOTP 2FA on npm in favor of FIDO-based auth with 7-day granular tokens. These are the most significant GitHub Actions security changes since the platform launched. Microsoft published detailed enterprise mitigation guidance with Defender detection queries and Sentinel hunting queries for the C2 infrastructure.

Meanwhile, an arXiv paper dropped the same week showing that code obfuscation defeats JavaScript SAST tools in CI/CD pipelines. So even if you have automated security scanning, an obfuscated supply chain payload could slip through.

What to do right now: check your lockfile for Axios 1.14.1 or 0.30.4. Rotate credentials if you installed either. Adopt GitHub's new dependency locking for Actions workflows. And start treating your npm dependency chain with the same paranoia you'd apply to a production database connection string, because that's what it is now.