Which versions of telemetry-metrics are malicious?

The following npm versions of telemetry-metrics are flagged malicious: 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5. Treat any of these as compromised.

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

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

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

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

Yes — telemetry-metrics is associated with the IN-MAL-2026-010771, IN-MAL-2026-010903, IN-MAL-2026-014941, IN-MAL-2026-015796, IN-MAL-2026-018271 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-metrics 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-metrics (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging telemetry-metrics across your stack and pipelines.

Malicious package

telemetry-metricsnpm

telemetry-metrics is a confirmed malicious npm package (MAL-2026-10750) that typosquats a legitimate package to trick installs (malicious versions 0.2.1, 0.2.2, 0.2.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in telemetry-metrics (npm)

MAL-2026-10750

Immediate action

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

npm uninstall telemetry-metrics

What this malware does

The package publishes as unscoped 'telemetry-metrics' while its README, repository, homepage, and bugs metadata all reference the legitimate @telemetry-js/telemetry project, and the bulk of the source is copied from that upstream. An added lib/plugin-options.js fetches https://raw.githubusercontent.com/ThoSuperstarDev/axios-http/main/lib/env/axios.exe (a mutable branch on an unrelated personal GitHub account), writes it to C:\Windows\http-axios.exe via fs.writeFileSync, and executes it via child_process.execFile. The pluginOptions function is invoked from lib/task.js on every plugin registration path (collect/process/publish/schedule/use), so ordinary library usage on Windows triggers the drop-and-run against the installer's host. The fetched binary is unpinned (mutable branch), unhashed, sourced from a publisher unrelated to the impersonated project, and staged into a system directory.

Malicious versions

5 flagged

0.2.10.2.20.2.30.2.40.2.5

Indicators of compromise (SHA-256)

2cd215db682d2cc6eb6c9d4f5f704b66503762047ac210160f07559c07e93dea

1bb843a52a3b9144f4ab2f1233e2f48671524217cf93b7e16a85c9f5551dedb7

3ca5a92b8a793861df4d3480ffa064564909421659b72e6a9bb1f6af72847f55

98464f7aa81782713f6ddc5c715a283eca2df8df51fa99d92b0b8f57dc1ba2d4

be4febbe54278c23fb18c8e97653087f66402b132f45929f2a8c1ebc65693f26

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

Campaign

IN-MAL-2026-010771IN-MAL-2026-010903IN-MAL-2026-014941IN-MAL-2026-015796IN-MAL-2026-018271

References

Credits

Amazon Inspector · finder

Detect & block this

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