Which versions of axios-fast are malicious?

The following npm versions of axios-fast are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate axios-fast if I installed it?

axios-fast is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed axios-fast — how do I know if it already compromised me?

If axios-fast was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is axios-fast part of a known attack campaign?

Yes — axios-fast is associated with the IN-MAL-2026-017776, IN-MAL-2026-017903 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find axios-fast across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for axios-fast (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axios-fast across your stack and pipelines.

Malicious package

axios-fastnpm

axios-fast is a confirmed malicious npm package (MAL-2026-14029) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in axios-fast (npm)

MAL-2026-14029

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall axios-fast

What this malware does

[email protected] declares a preinstall lifecycle script in package.json that runs a Node one-liner which POSTs the entire process.env of the installing machine to a hardcoded webhook.site inbox (https://webhook.site/31e82bcd-a220-42e6-82f0-4f082e8fa80e/). The script fires automatically on npm install, before any code is reviewed, and dumps all environment variables — routinely including AWS_*, NPM_TOKEN, GH_TOKEN, and other CI/build secrets — to a third-party attacker-controlled endpoint. The package name typosquats the popular axios HTTP client but its shipped functionality is limited to this install-time exfiltration.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

fb41ba4304bae7ef1cc71fa25060b50c201e51bee9989b1e34a0515fc1d31829

9cc76e819084a35126e067bd65bd3cf2fc52b6d8e068b67d14360ef71505fa7e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for axios-fast (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axios-fast across your stack and pipelines.
If you installed it — respond
axios-fast is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If axios-fast was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks axios-fast before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. axios-fast on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017776IN-MAL-2026-017903

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks axios-fast-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database