MAL-2026-13948 Malicious code in debug-proxy-chrome-devtools (npm)
Malicious package
Published
MAL-2026-13948 is a malicious package: debug-proxy-chrome-devtools (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-13948/ (Markdown: https://insights.sbomify.com/MAL-2026-13948/index.md)
- Package
- debug-proxy-chrome-devtools
- Registry
- npm
What is MAL-2026-13948?
MAL-2026-13948 is a malicious package in debug-proxy-chrome-devtools, published on 13 Aug 2026.
Official description
[email protected] declares a postinstall hook (
"postinstall": "node install.js") that automatically executes on npm install. install.js uses child_process.execSync to run whoami on the installer's machine and then issues an https.get to a hardcoded webhook.site collector (https://webhook.site/cfe35ac2-bec3-48b8-bae1-a49dea5412c2), passing the captured command output and hostname/command identifiers as URL query parameters. The package advertises itself as a Chrome DevTools debug proxy; that stated purpose has no need for shell reconnaissance or beaconing to a third-party request-inspection service. The combination of automatic install-time execution, capture of installer-side identity data, and a hardcoded non-first-party exfiltration endpoint matches the reconnaissance/beacon shape of a malicious postinstall payload.What should I do about MAL-2026-13948?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.