Notifications
Clear all
Topic starter
19/08/2026 3:37 pm
TL;DR: Malicious axios versions 1.14.1 and 0.30.4 were published through a hijacked maintainer account, injecting a hidden dependency that drops a cross-platform RAT and self-erases to evade inspection, according to StepSecurity. The incident shows how trusted package identities, OIDC publishing patterns, and developer install paths can be abused faster than manual review can respond.
NHIMG editorial — based on content published by StepSecurity covering the axios npm compromise: Malicious versions drop a remote access trojan through hijacked maintainer credentials
By the numbers:
- axios is the most popular JavaScript HTTP client library with over 100 million weekly downloads.
Questions worth separating out
Q: What breaks when package publishing identities are compromised?
A: When publishing identities are compromised, the attacker can release malicious packages that inherit the trust of a real project.
Q: Why do hidden dependencies make npm supply chain attacks so dangerous?
A: Hidden dependencies let attackers introduce executable behaviour without changing the visible application code.
Q: How do you know if package security controls are actually working?
A: Look for fewer unexpected publishes reaching build systems, lower rates of install-time outbound connections, and measurable reductions in secret exposure during pipeline execution.
Practitioner guidance
- Enforce trusted publishing for package releases Require cryptographically verifiable publishing paths such as OIDC-linked workflows for all internal and third-party package releases, and alert on any manual publish that diverges from the approved pattern.
- Block or review install hooks Prevent postinstall scripts from running in high-trust pipelines unless the package and maintainer identity have passed explicit approval, because install-time code execution is where the compromise becomes active.
- Add egress controls to CI and developer devices Use outbound allowlisting and DNS or process telemetry to detect package installs that reach unknown command-and-control infrastructure, especially when the package later deletes its own artifacts.
What's in the full analysis
StepSecurity's full post covers the operational detail this post intentionally leaves for the source:
- File-level diff analysis of the malicious dependency and the exact postinstall mechanics used to trigger execution
- Registry metadata evidence showing how the poisoned publish diverged from the normal trusted-publisher pattern
- Indicators of compromise, affected version guidance, and remediation steps for CI runners and developer machines
- Detection logic and workflow telemetry examples from Harden-Runner that show how the C2 callback was flagged
👉 Read StepSecurity's analysis of the axios npm supply chain compromise →
Axios npm compromise: what the maintainer hijack means for teams?
Explore further
19/08/2026 4:17 pm
Trusted publisher identity is now a control plane, not a metadata field. The axios compromise shows that package provenance is only as strong as the identity used to publish it. When a maintainer token or account is hijacked, the attacker inherits distribution trust, not just repository access. Identity governance teams should treat software publishing accounts, OIDC bindings, and registry privileges as high-value NHI assets that require lifecycle controls, not ad hoc administration.
A few things that frame the scale:
- 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities.
A question worth separating out:
Q: Who is accountable when a malicious package reaches production systems?
A: Accountability usually sits across security, engineering, and platform operations. Engineering controls the dependency choices, security defines the detection and response requirements, and platform teams govern build pipelines and package trust policies. Frameworks such as NIST CSF, NIST 800-53, and MITRE ATT&CK support shared ownership of prevention, detection, and response.
👉 Read our full editorial: Axios supply chain compromise shows how hijacked npm identities spread RATs
