Axios RAT: North Korean Sophistication, Platform-Specific Payloads, and the Lockfile Defense That Actually Worked

Microsoft Attributes Axios npm RAT to Sapphire Sleet with Full IOC Disclosure

Microsoft formally names Sapphire Sleet (North Korean APT) behind the Axios 1.14.1 and 0.30.4 compromise, publishing the C2 infrastructure, SHA-256 hashes, and platform-specific payload paths. If you haven't rotated credentials and patched to 1.14.0 or 0.30.3 yet, this is the authoritative checklist to work from.

Snyk's Axios Incident Breakdown: Lockfiles Are Your First Line of Defense

Snyk's writeup confirms lockfile integrity was the single control that separated unaffected projects from compromised ones during the roughly 3-hour exposure window. The practical CLI commands for auditing bun.lock, yarn.lock, and package-lock.json make this the most actionable remediation guide for developers.

Phoenix Security Full Kill Chain: How the Axios Attack Bypassed OIDC Trusted Publishing

The most technically detailed reconstruction available, showing the attacker bypassed axios's GitHub Actions OIDC pipeline entirely by using a stolen long-lived npm token. The StepSecurity Harden-Runner telemetry proving C2 contact happened 1.1 seconds into npm install is the clearest evidence of how fast this fires.

Agentic AI Doubles the Axios Supply Chain Blast Radius

IronPlate flags a risk most teams haven't priced in: AI coding agents like Claude Code and Cursor run npm install autonomously, meaning the RAT deploys with zero human approval in the loop. If your agents have MCP connections with broad filesystem access, a compromised dev machine becomes a pivot point into every connected system.