Malicious code in utility-kit-ts (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-12493
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (11d4f4654f1acbc26d30e2ea0cae4816bf6e3a847dce2456134d050a38a8a575) The package's default export getPlugin issues a fetch to the hardcoded bare-IP URL https://31.97.137.157:45000/icons/109 and passes the returned data.credits field to the Function constructor, then invokes the compiled function with require, module, process, Buffer and other Node primitives bound in. Any code the remote host returns executes in the caller's Node.js process with full library privileges. A separate function setDefaultModule constructs a plausible cdnjs/font-awesome URL from an icon-domain map but is never called from any export, serving as decoy alongside the actual bare-IP eval sink. The package is advertised in its README as a zero-dependency TypeScript utility toolkit, but package.json declares dependencies (@primno/dpapi for Windows DPAPI unwrap, better-sqlite3, node-machine-id, socket.io-client, request) that are inconsistent with utility helpers and are pre-staged for the fetched payload to require — the building blocks of a credential/browser-cookie stealer. ## Source: ghsa-malware (e4d47d251f81b0696dd32c48deec7ce497f8f72b3681dd774ea4446e11d0336e) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 5 Aug 2026 12:24:20 UTC
- Source modified
- 6 Aug 2026 01:21:43 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.