{"id":"MAL-2026-13948","revision":"d2cbdf8c7ba84e26b296d9a542398bc9","records":[{"revision":"d2cbdf8c7ba84e26b296d9a542398bc9","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13948","aliases":[],"title":"Malicious code in debug-proxy-chrome-devtools (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (b7a0986932a47f49b162ea0438acfd0b6293e027e8ac2da46eb1221c5d52646c)\ndebug-proxy-chrome-devtools@1.0.1 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.\n","state":0,"publishedAt":"2026-08-13T17:16:22+00:00","modifiedAt":"2026-08-13T17:30:12.5395701+00:00","affected":[{"ecosystem":"npm","name":"debug-proxy-chrome-devtools","ranges":[],"versions":["1.0.2","1.0.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/debug-proxy-chrome-devtools/v/1.0.2","https://www.npmjs.com/package/debug-proxy-chrome-devtools/v/1.0.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13948","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13948","identifiers":["MAL-2026-13948"]},"retained":false,"historicalAffected":[]}],"coverage":[]}