MAL-2026-15924 Malicious code in real-router-telemetry (npm)
Malicious package
Published
MAL-2026-15924 is a malicious package: real-router-telemetry (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-15924/ (Markdown: https://insights.sbomify.com/MAL-2026-15924/index.md)
- Package
- real-router-telemetry
- Registry
- npm
What is MAL-2026-15924?
MAL-2026-15924 is a malicious package in real-router-telemetry, published on 4 Sep 2026.
Official description
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.What should I do about MAL-2026-15924?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.