Malicious code in ts-toolkit-plus (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-12812
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (49d47be3f5dc16ea70755e0233f46106d3f50d1d5384a4f20c76b91463c9876c) The package's main entry defines a getPlugin() function that performs an HTTPS request to a hardcoded bare-IP endpoint at 31.97.137.157:45000/icons/112 and passes the response field data.credits to `new Function('require','module',...,'Promise', data.credits)`, executing whatever the remote host returns with full Node.js context including require, process, Buffer, and globalThis. The destination URL is assembled from split protocol/separator/domain/path fragments and wrapped in benign 'icon/CDN' naming that hides the code-execution sink. The declared dependencies (@primno/dpapi for Windows DPAPI unwrap of browser-stored secrets, node-machine-id for host fingerprinting, better-sqlite3/sqlite3 for browser profile databases, socket.io-client) do not correspond to the advertised 'crypto checkout' purpose and pre-stage tooling a remote payload can invoke via the injected require() to harvest Windows browser credentials and cookies. Any consumer that require/imports this package and reaches the getPlugin path grants the remote operator arbitrary code execution on the installer's machine. ## Source: ghsa-malware (cad454e0e312c87020333f7ece00363eb627c8b1b1334431c662c09a6af7dad1) 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 13:14:43 UTC
- Source modified
- 6 Aug 2026 01:21:41 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.