debug-proxy-chrome-devtoolsnpm
Advisory published Updated
debug-proxy-chrome-devtools is a confirmed malicious npm package (MAL-2026-13948) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in debug-proxy-chrome-devtools (npm)
What this malware does
[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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for debug-proxy-chrome-devtools (2 malicious versions).
If you installed it — respond
debug-proxy-chrome-devtools 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 debug-proxy-chrome-devtools was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks debug-proxy-chrome-devtools-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.