Which versions of real-router-telemetry are malicious?

The following npm versions of real-router-telemetry are flagged malicious: 1.0.1, 1.0.4. Treat any of these as compromised.

How do I remediate real-router-telemetry if I installed it?

real-router-telemetry 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 real-router-telemetry — how do I know if it already compromised me?

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

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

Malicious package

real-router-telemetrynpm

real-router-telemetry is a confirmed malicious npm package (MAL-2026-15924) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in real-router-telemetry (npm)

MAL-2026-15924

Immediate action

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

npm uninstall real-router-telemetry

What this malware does

Package ships telemetry.js, an obfuscated module (string-array accessor pattern hiding identifiers and the destination) that reads host identity (hostname, username, cwd, platform, arch, memory, cpu info), executes cat /etc/os-release and ps aux, reads .env from the current working directory via fs.readFileSync, and POSTs the collected JSON to https://webhook.site/e32d3b8a-a5df-40cc-ae60-7a8343b581e4, an anonymous request-capture endpoint unrelated to any declared publisher. .env files in a developer's cwd typically contain API keys, tokens, and other credentials that do not belong to this package. package.json declares a postinstall hook (node -e "require('./index.js')"); index.js in this build is a stub (declaring version 1.0.1 while the manifest is 1.0.4) that does not currently require telemetry.js, so the shipped payload is staged but not wired into the install-time entry point in this version. The combination of an obfuscated host-and-secret exfil module targeting an anonymous webhook collector, mismatched version metadata, and an install-time hook aimed at the package's own entry point indicates a malicious package.

Malicious versions

2 flagged

1.0.11.0.4

Indicators of compromise (SHA-256)

339c7fb3c40f724b7ec7c2ac3c67068b03f9d871ec65876913795cff3c2d9537

78bc9af22f0b3feafc2dbd863d7ce4b9ba26418ab58e87bc231123004a40a450

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

Campaign

IN-MAL-2026-019635IN-MAL-2026-019634

References

Credits

Amazon Inspector · finder

Detect & block this

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