Which versions of v018-axios-cdntest are malicious?

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

How do I remediate v018-axios-cdntest if I installed it?

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

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

Yes — v018-axios-cdntest is associated with the IN-MAL-2026-005288, IN-MAL-2026-005346, IN-MAL-2026-005354, IN-MAL-2026-005353 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 v018-axios-cdntest 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 v018-axios-cdntest (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging v018-axios-cdntest across your stack and pipelines.

Malicious package

v018-axios-cdntestnpm

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

MAL-2026-5529

Immediate action

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

npm uninstall v018-axios-cdntest

What this malware does

Package impersonates axios v0.18.0 (index.js carries the genuine axios v0.18.0 | (c) 2018 by Matt Zabriskie header and sets window.axios={}, window.__cdn_package='[email protected]') but ships two malicious payloads. (1) index.js appends an IIFE that reads document.cookie and sends it via XMLHttpRequest GET to a hardcoded webhook.site endpoint (https://webhook.site/ef6e7978-f936-4664-b3ff-296a250e1735?c=<cookies>), firing on the page load event so any consumer loading this script via CDN or bundle leaks all accessible cookies to the attacker. (2) Sibling xmr-min.js is an in-browser Monero cryptojacker that constructs a Web Worker from a Blob and uses eval on dynamic JS to mine to wallet 44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A via pool.supportxmr.com:4444. The package is intended to be loaded through jsdelivr (cdn.jsdelivr.net/npm/v018-axios-cdntest@.../xmr-min.js), so any site embedding it leaks user cookies and burns visitors' CPU. The package's own description self-labels these payloads.

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

a591698b95bbe1180b694b6aac6d31e658b4fd1e0ba9941f7a9714e223a0ab79

67d30d2c9939173663f8ba1312b2591d2f86c67657bd5eeff59b19187f50b901

c1d75c09e9ea65962971d748fe0dd6a3ba162626453ba13b017dddee2bd73efa

9dc3747912c6afcf740e0b3600533ffde67565b8d6dbfcd192750f45d3625e13

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 v018-axios-cdntest (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging v018-axios-cdntest across your stack and pipelines.
If you installed it — respond
v018-axios-cdntest 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 v018-axios-cdntest 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 v018-axios-cdntest 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. v018-axios-cdntest on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005288IN-MAL-2026-005346IN-MAL-2026-005354IN-MAL-2026-005353

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks v018-axios-cdntest-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