Which versions of telemetry-axios are malicious?

The following npm versions of telemetry-axios are flagged malicious: 0.1.5, 0.1.6. Treat any of these as compromised.

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

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

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

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

Yes — telemetry-axios is associated with the GHSA-89mf-39r2-ff96, IN-MAL-2026-011152, IN-MAL-2026-011154 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 telemetry-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 telemetry-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 telemetry-axios across your stack and pipelines.

Malicious package

telemetry-axiosnpm

telemetry-axios is a confirmed malicious npm package (MAL-2026-10773) that typosquats a legitimate package to trick installs (malicious versions 0.1.5, 0.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in telemetry-axios (npm)

MAL-2026-10773

Immediate action

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

npm uninstall telemetry-axios

What this malware does

The package's Control.plugin() entry point calls PluginOptions(), which fetches a binary payload from https://raw.githubusercontent.com/ThoSuperstarDev/axios-http/main/lib/env/axios-telemetry.json — a personal GitHub repository on a mutable main branch, unrelated to the declared publisher. The response bytes (URL extension is.json, but the content is a Windows PE) are written to %LOCALAPPDATA%/Temp/msedgewebview2.exe, impersonating the Microsoft Edge WebView2 runtime binary, and then executed via execFile with no hash or signature verification. The package name mimics the popular axios/telemetry ecosystem, and the dropper mechanism has no relation to the package's stated 'modular metrics' purpose. Any consumer that invokes the advertised.plugin() API downloads and runs attacker-controlled code on the host.

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.

Malicious versions

2 flagged

0.1.50.1.6

Indicators of compromise (SHA-256)

15daf7bcf2af06908cb74f81166241c5c3534e75c609204e81b984f6cd3ee867

0f21f282e7349c68d7ff17d0b5c452fb51c3bab106ffb6f56dc80f108c4b0800

07dadbdcf4e20f6e1fb39be1cc1d17222abd2855242baabe00aa40f054676a35

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 telemetry-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 telemetry-axios across your stack and pipelines.
If you installed it — respond
telemetry-axios is a typosquat — you almost certainly intended a legitimately-named package. Remove telemetry-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 telemetry-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 telemetry-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. telemetry-axios on npm has been identified as a malicious package (versions 0.1.5, 0.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-89mf-39r2-ff96IN-MAL-2026-011152IN-MAL-2026-011154

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks telemetry-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

Explore

All malware advisories How O3 detects malware Vulnerability database