Malicious code in @nextco/utils (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-12325
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2af3efee911b20157dcf0e84f2be91affddf4e34aac298e1959ea7090f08c4d2) On require(), index.js unconditionally calls a telemetry() function at module top level that collects host reconnaissance (hostname, username, __dirname, cwd, OS/arch, Node version) and the list of environment variable names, base64-encodes the payload, and POSTs it over plain HTTP to the hardcoded host attacker.cl. The destination is not associated with the package's stated publisher (@nextco/utils / nextco.me) and the caller has no opt-out. The behavior fires simply by loading the module, giving an attacker installer host identifiers and an env-var name inventory usable to target follow-on credential theft.
- Source published
- 5 Aug 2026 13:07:46 UTC
- Source modified
- 5 Aug 2026 13:35:12 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.