Malicious code in checkout-public-tokens (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-12589
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c1ca81222c080449cad71d071579738ea810e280c6e8ed3b53647efdde902536) On require() of checkout-public-tokens, index.js loads _platform.js which downloads an opaque binary payload from hardcoded string-split-obfuscated hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev), with a DNS-TXT base64 fallback resolver via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The payload is written to /tmp or %TEMP% under a disguised name (.cache_<hex> or dotnet_diag_<hex>.exe), chmodded to 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are constructed at runtime by joining split literals, and in-file comments frame the download-and-execute chain as telemetry, analytics, and cache validation. The package advertises itself as a token utility; the hosts and behavior are unrelated to any documented purpose and there is no hash or signature verification of the fetched bytes.
- Source published
- 5 Aug 2026 14:09:28 UTC
- Source modified
- 5 Aug 2026 14:35:38 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.