Axios npm Supply Chain Attack: North Korean RAT, CI/CD Blind Spots, and What to Do Now

Analysis

Microsoft Attributes Axios npm Compromise to North Korean Sapphire Sleet Actor

Microsoft Threat Intelligence pinned the Axios supply chain attack on Sapphire Sleet, a North Korean state-sponsored group, and confirmed a second-stage cross-platform RAT was deployed on macOS, Windows, and Linux. The key action item: downgrade to axios 1.14.0 or 0.30.3 and disable auto-updates immediately since the malware includes a hook that keeps trying to update.

Datadog Security Labs Deep Dive: How the Axios Maintainer Account Was Hijacked and the RAT Deployed

Datadog's technical breakdown is the most detailed forensic write-up so far, tracing exactly how the attacker bypassed CI/CD by publishing via a stolen long-lived npm token instead of GitHub Actions OIDC, making the attack invisible to anyone watching the GitHub repo. They also flag that the Windows and Linux RAT payloads contain bugs, and that most package managers now support a dependency cooldown setting worth enabling.

Full Attack Timeline and IOCs for the Axios npm Compromise

This breakdown reconstructs the full sequence of events minute by minute, identifies the trojanized dependency plain-crypto-js, and confirms the malicious versions existed only on the npm registry with zero corresponding GitHub commits. If you need the IOCs and a remediation checklist in one place, this is the fastest read.

News

SANS Institute Incident Guidance for the Axios Supply Chain Attack

SANS published practitioner-focused guidance covering who is affected, how to check lockfiles, and what incident response steps to take if your environment installed either compromised version. Worth forwarding to your security and DevOps teams as a concise action checklist.

3% of Affected Environments Saw Active RAT Execution During the 3-Hour Axios Exposure Window

Wiz telemetry cited in this piece shows that despite the packages being live for only about three hours, observed RAT execution occurred in 3% of affected environments, which is a significant hit rate for a short window. The attacker's permissions also exceeded the maintainers' own access, briefly locking the legitimate team out of the project.