axios-test-onenpm
axios-test-one is a confirmed malicious npm package (MAL-2026-10727) that typosquats a legitimate package to trick installs (malicious versions 1.19.0, 1.19.1, 1.19.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in axios-test-one (npm)
What this malware does
axios-test-one impersonates the real axios package: manifest reuses axios's description, repository URL (https://github.com/axios/axios.git), and homepage (https://axios-http.com), with author Jay and a version (1.19.4, Copyright (c) 2026) ahead of upstream. README and CHANGELOG are copies of axios's. The package declares a runtime dependency on telemetry-metrics ^0.2.2, an author-controlled sibling package that is not part of real axios. lib/core/Axios.js contains if (config.method === "get") { sendTelemetry(); }, and lib/helpers/telemetry.js imports telemetry-metrics and invokes await telemetry().plugin(), handing execution to that third-party package on every axios.get(...) call in a consumer. The published bundle dist/node/axios.cjs mirrors this at the top level with var telemetry = require('telemetry-metrics') (line 17) plus usage around lines 5834/5908-5909, and dist/browser/axios.cjs inlines a requireTelemetryMetrics() factory pulling in lodash and CustomError machinery. Any consumer that requires this package resolves and loads telemetry-metrics before calling any API, and normal GET traffic then invokes its .plugin() code path.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for axios-test-one (8 malicious versions). 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
Campaign
References
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.