Malicious code in checkout-common-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-12351
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fe0e9681cb5e7a197ca8d77ba29e20a4709fa0ff476f2ffb02f935785c6633e0) On require, index.js loads _ext.js which selects a platform-specific payload URL from a rotating list of Cloudflare Workers subdomains (hosts assembled at runtime by joining split string fragments such as ["oob-worker.cf101-adf.workers.d","ev"].join("")), fetches the binary over HTTPS, writes it to /tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods 0o755, and spawns it detached via /bin/sh -c or cmd.exe. If the HTTPS fetch fails, _ext.js falls back to a DNS-TXT covert channel against *.dl.well1.site: a chunk-count TXT lookup at c.<domain> followed by N.<domain> TXT queries whose base64-decoded concatenation is written to disk and executed. Staging file names (.cache_*, dotnet_diag_*.exe,.analytics_state) are chosen to mimic legitimate diagnostic/telemetry artifacts, and destination hostnames are string-split obfuscated to defeat static inspection. The fetched payload is opaque, unpinned, unrelated to any documented package purpose, and executed with the installer's privileges immediately on import. ## Source: ghsa-malware (63365b713418a63ac55d381e309bd078a837b9059328608cf6c3619faafe6445) 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:36:29 UTC
- Source modified
- 18 Aug 2026 12:45:11 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.