This package has dated incident reports relevant to its trust history. Check the affected releases and the response before drawing conclusions about its current version.
Read the incident coverage →Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Loading historical repository activity…
Signals · last 31 checks
Dated reporting about this package. These events are separate from its current maintenance score.
· npm
StepSecurity traced two malicious Axios releases to compromised publishing credentials. A newly added dependency delivered the payload; the affected releases were subsequently removed from npm.
Affected versions: 1.14.1 and 0.30.4
Packages: axios
Source: StepSecurity
Third-party facts checked 2 days ago; registry facts on every crawl.
| When | Change |
|---|---|
| 2026-11-05 | first verdict: active |
account hijacked 2026-03 1.14.1, 0.30.4
The lead maintainer was socially engineered through a fake workspace and call into installing a trojan; the attacker then published two versions that added a never-imported dependency whose post-install script dropped a remote-access tool.
npm removed the packages about three hours later and revoked tokens; the maintainer published a post-mortem.
Source: Datadog Security Labs analysis and the maintainer’s post-mortem, 31 March 2026. History, not a warning about today — the verdict above is about maintenance now.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/axios)Watch it
Get told when axios changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.