Axios npm Supply Chain Attack Delivers Cross‑Platform RAT

Affected Environment
Organisations using axios npm 1.14.1 or 0.30.4, and any build chains that pulled these. Any environment with node_modules/plain-crypto-js present should be treated as exposed.

Threat Overview
Attackers hijacked the axios npm package using a stolen token and added a ghost dependency. The dependency deployed a cross-platform RAT with anti-forensic “self-healing” behaviour.

Exposure Timeline
Malicious plain-crypto-js and axios versions were published late 30–31 March 2026. npm removed the axios versions and placed a security hold on the dependency on 31 March.

Attack Surface
Exposure exists wherever compromised axios versions or plain-crypto-js were installed. Both direct and transitive npm dependencies increase the likelihood of silent adoption.

Technical Root Cause
Attackers used a long-lived npm access token to bypass GitHub OIDC safeguards. Malicious packages were manually published, missing trustedPublisher and gitHead fields.

Exploitation Pathway
Installing the backdoored axios versions pulled in plain-crypto-js as a ghost dependency. Its RAT executed, then altered local package metadata to disguise the malicious version.