Which versions of axios-cancelable are malicious?

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

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

axios-cancelable 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-cancelable — how do I know if it already compromised me?

If axios-cancelable 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-cancelable part of a known attack campaign?

Yes — axios-cancelable is associated with the GHSA-7h7g-wg9p-wf94 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-cancelable 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-cancelable (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-cancelable across your stack and pipelines.

Malicious package

axios-cancelablenpm

Malicious code in axios-cancelable (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191389

Immediate action

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

npm uninstall axios-cancelable

What this malware does

The package axios-cancelable was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

75d14fc368f245f979b9985e3d9504dbd4c302b8b7c7644d345d642daffe78c2

34b03d17fe2a4d83f67cbda737712693abb19fc4da135fab010adb7aeeb82ddd

7210c0ae0996b1026ba173fc3f0628154433a7a8ba971106d24dab744d6d28ec

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-cancelable (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-cancelable across your stack and pipelines.
If you installed it — respond
axios-cancelable 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-cancelable 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-cancelable 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-cancelable on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7h7g-wg9p-wf94

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks axios-cancelable-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