Notifications
Clear all
Topic starter
19/08/2026 3:48 pm
TL;DR: Attackers compromised the axios maintainer’s npm account in June 2026, published malicious versions that hid a postinstall RAT, and created a supply-chain event that could reach any project pulling fresh dependencies, according to Arnica’s analysis. The lesson for practitioners is that lockfiles, cooldowns, and runtime egress controls now matter as much as repository scanning.
NHIMG editorial — based on content published by Arnica: How to Check for Impacted axios Packages in Your SBOM
By the numbers:
- The malicious releases of axios were published after the attacker compromised the maintainer account on March 30, 2026, and both versions were later removed from the registry.
- Axios has more than 100 million weekly downloads, making compromise of its maintainer account a high-reach supply-chain event.
Questions worth separating out
Q: What breaks when malicious npm packages execute on import instead of install?
A: Install-time controls often miss import-time payloads because the malicious code lives in the published bundle and runs when the module loads.
Q: Why do maintainer accounts become high-value targets in software supply chains?
A: Because one maintainer identity often controls publishing rights, package metadata, and downstream trust.
Q: How do security teams know whether a dependency compromise reached production?
A: They need to combine SBOM review, lockfile inspection, CI build logs, endpoint telemetry, and outbound network monitoring.
Practitioner guidance
- Enforce package cooldowns across build systems Set a minimum release age in npm, pnpm, yarn, bun, or your dependency management tooling so newly published versions cannot be pulled into unattended builds immediately.
- Treat maintainer tokens as privileged identities Inventory maintainer accounts, package publish tokens, and automation credentials used to release software.
- Scan SBOMs and lockfiles for the impacted versions Search for [email protected], axios@0.30.4, and plain-crypto-js in package-lock.json, yarn.lock, bun.lockb, and container artefacts.
What's in the full article
Arnica's full analysis covers the operational detail this post intentionally leaves for the source:
- Exact package names, version numbers, and indicators of compromise for SBOM and registry searches
- Step-by-step remediation guidance for build hosts, local workstations, and CI runners after exposure
- Package-manager configuration examples for cooldown policies in npm and pnpm
- Additional supply-chain hardening settings for teams that use automated dependency tools
👉 Read Arnica's analysis of the axios maintainer compromise and malicious npm releases →
Axios package compromise: what should SBOM teams do now?
Explore further
19/08/2026 4:24 pm
Package publisher identity is now part of the non-human identity estate. A maintainer token or registry account is not just a development convenience. It is a privileged identity that can alter software supply chains at scale, and its compromise can create downstream access to code execution, secrets, and build pipelines. For identity teams, that means publisher accounts deserve the same lifecycle scrutiny as service accounts and automation tokens.
A few things that frame the scale:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes, and as quickly as 9 minutes in some cases, according to LLMjacking: How Attackers Hijack AI Using Compromised NHIs.
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities.
A question worth separating out:
Q: Should teams rely on SBOMs alone to manage malicious package exposure?
A: No. SBOMs identify presence, but they do not show execution, exfiltration, or compromised credentials. The better model is inventory plus containment, meaning lockfile control, cooldowns, egress blocking, and rapid token rotation after any confirmed malicious install. That combination limits both reach and dwell time.
👉 Read our full editorial: Compromised npm maintainer accounts turn SBOM review into triage
