debug-proxy-chrome-devtools
Affected
- Versions:
1.0.1,1.0.2
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in debug-proxy-chrome-devtools (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (b7a0986932a47f49b162ea0438acfd0b6293e027e8ac2da46eb1221c5d52646c)
[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.
Not rated by the source.
1.0.1, 1.0.2None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0