Which versions of axios-test-one are malicious?

The following npm versions of axios-test-one are flagged malicious: 1.19.0. Treat any of these as compromised.

How do I remediate axios-test-one if I installed it?

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

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

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

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

Malicious package

axios-test-onenpm

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

MAL-2026-10727

Immediate action

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

npm uninstall axios-test-one

What this malware does

[email protected] impersonates the real axios package (ships axios's README/CHANGELOG verbatim, bundles are stamped /*! Axios v1.18.9 Copyright (c) 2026 Jay and contributors */, and declares axios's own repository/homepage URLs) while adding an undeclared runtime dependency on telemetry-metrics@^0.2.1. lib/helpers/telemetry.js does import telemetry from "telemetry-metrics"; export function sendTelemetry(){ telemetry().plugin(); }, and lib/core/Axios.js invokes sendTelemetry() from _request whenever config.method === 'get'. Any code shipped by the third-party telemetry-metrics package therefore executes in the consumer's Node.js process on the first axios.get(...) call, giving that package arbitrary code execution in the installer's runtime under cover of the axios API surface.

Malicious versions

1 flagged

1.19.0

Indicators of compromise (SHA-256)

5f53cd512e7aa0549f6ff4ae3064dc13fd8d72c8dddc464f7639376abfadc4a6

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 axios-test-one (version 1.19.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axios-test-one across your stack and pipelines.
If you installed it — respond
axios-test-one is a typosquat — you almost certainly intended a legitimately-named package. Remove axios-test-one, 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 axios-test-one 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-test-one 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-test-one on npm has been identified as a malicious package (version 1.19.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010773

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks axios-test-one-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