Malicious code in system-performance-helper (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-14194
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f382b23398f0b2550e29a61c444b8dbd45796d20c938dead6ada9d967d82cabc) Package advertises itself as a system performance monitoring helper, but its package.json declares a postinstall hook (`node install.js`) that opens a TCP socket and pipes a spawned OS shell (`/bin/sh` on Unix, `cmd.exe` on Windows) stdin/stdout/stderr through it, with auto-reconnect and a keep-alive interval — a canonical reverse-shell backdoor executed automatically on `npm install`. Bytes received from the remote peer are written directly into the shell, yielding full remote code execution on the installer's host. The destination is hardcoded as `HOST="YOUR_PUBLIC_IP"`, `PORT=4444`, so as-published the connect() fails DNS resolution and no callback occurs; the payload itself is fully functional and any republish with the placeholder filled in weaponizes every install. The visible exports in index.js (`getLoad`, `getTotalMemory` wrapping `os.loadavg`/`os.totalmem`) are a cover story; install.js contains `// Run silently` and `// Fail quietly` comments around the socket-to-shell pipe, and the advertised monitoring behavior is not present in the postinstall payload.
- Source published
- 19 Aug 2026 01:16:23 UTC
- Source modified
- 24 Sep 2026 09:41:10 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.