Notifications
Clear all
Topic starter
19/08/2026 3:48 pm
TL;DR: Axios was compromised through its maintainer access, and malicious npm releases briefly delivered a RAT across Windows, macOS, and Linux systems, with Expel noting detection within about 22 minutes of the package going live. The incident shows how quickly trusted dependency ecosystems can turn credential theft and code execution into enterprise-wide exposure.
NHIMG editorial — based on content published by Expel: LLMjacking: How Attackers Hijack AI Using Compromised NHIs
By the numbers:
- Expel first saw an alert from one of our custom detections about this hitting a customer at approximately 2026-03-31T00:50:00 UTC, about 22 minutes after the package went live.
- The malicious package was active from March 31 00:21 UTC to 03:15 UTC, creating a short but high-impact exposure window.
Questions worth separating out
Q: What breaks when a trusted npm package publisher is compromised?
A: When a trusted publisher is compromised, registry trust collapses because malicious code can arrive through a legitimate release path.
Q: Why do package compromises often lead to credential theft?
A: Package compromises often lead to credential theft because developers and build hosts commonly store access tokens, cloud keys, and SSH material in reachable locations.
Q: How do security teams know if a package compromise is actually contained?
A: They should confirm three things: the bad version no longer appears in lockfiles, SBOM records no longer resolve to it, and running services no longer load it.
Practitioner guidance
- Audit package publishing trust chains Review who can publish, approve, or transfer ownership for critical npm packages, and require phishing-resistant MFA plus release attestation for maintainers.
- Hunt for post-install script execution Search developer and CI endpoints for suspicious curl, PowerShell, Python, or temporary file execution associated with the compromise window.
- Revoke and rotate exposed credentials Assume npm tokens, AWS access keys, SSH private keys, and any other host-resident secrets on impacted systems are compromised until proven otherwise.
What's in the full analysis
Expel's full article covers the operational detail this post intentionally leaves for the source:
- Timeline analysis for the malicious Axios versions and the exact activity window to support hunts.
- Platform-specific command sequences for Windows, macOS, and Linux that defenders can use to validate telemetry.
- Operational remediation guidance for treating host-resident tokens, SSH keys, and AWS credentials as compromised.
- SOC response context showing how Expel built threat hunts and customer communications around the event.
👉 Read Expel's analysis of the Axios npm supply chain attack →
Axios npm compromise: what it means for supply chain controls?
Explore further
19/08/2026 4:25 pm
Supply chain trust is now an identity problem, not only a software integrity problem. When package maintainer access is abused, the attacker inherits the authority of a trusted release path and can turn a normal update into executable compromise. That makes publishing identity, signing identity, and developer workstation identity part of the same control surface. Practitioners should treat package provenance as an access-control question, not just a code-review issue.
A few things that frame the scale:
- 64% of valid secrets leaked in 2022 are still valid and exploitable today, according to The State of Secrets Sprawl 2026.
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers.
A question worth separating out:
Q: Who is accountable when secrets are exposed through compromised infrastructure software?
A: Accountability usually spans infrastructure owners, identity teams, and incident responders because the risk crosses software patching, credential governance, and detection coverage. Frameworks such as NIST CSF and NIST SP 800-53 expect clear ownership for protection, monitoring, and remediation. If no team owns the exposed secrets, the incident will be repeated in another form.
👉 Read our full editorial: Axios npm supply chain attack exposes how package trust fails
