Malicious code in poc-ch4rlygr (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-13454
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (341e5cb63d816ed6a8ed092f3b174e9826e10d051d8e78a53f0564b1437d0e04) On require()/import, index.js collects os.hostname(), os.arch(), __dirname, os.userInfo().username, and the full contents of process.env (serialized via Object.entries(process.env)) and issues an HTTPS GET carrying that data as a querystring to the hardcoded host zuxsp9k9vyk5y45z1n2hv0orhin9b2zr.oastify.com (a Burp Collaborator / OAST subdomain identified in-source as the receiver). Any secrets present in the installer's environment at load time (AWS_*, NPM_TOKEN, GITHUB_TOKEN, CI provider tokens, etc.) are leaked verbatim to that endpoint. package.json also declares a postinstall of `node tu-script.js`, but tu-script.js is not shipped in the tarball; the import-time module code is the operative exfiltration path.
- Source published
- 6 Aug 2026 19:09:42 UTC
- Source modified
- 6 Aug 2026 23:50:18 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.