Malicious code in devplatform-i18n (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-12714
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (30b21acc89730541bc58390e2694a9e5410417e5232bb4f4d47c0c27b035e2f4) Package is published as an i18n library but its main entry (index.js) requires./setup on load. setup.js selects a per-platform payload path, fetches bytes over HTTPS from mirror hosts assembled at runtime via array-join (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS TXT chunked base64 fallback via subdomains of wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru). The fetched bytes are written to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c '<path> &' or cmd /c start. A stamp file rate-limits re-execution. A parallel loader in lib/telemetry.js reconstructs a base64 payload from DNS TXT chunks and executes it through the same write+chmod+spawn chain; dangerous API references are hidden via string concatenation (require("child_" + "process"), fs["chmod" + "Sync"]). Destination hosts, module names, and filesystem APIs are all obfuscated via array-join and string concatenation, and the dropped filenames mimic OS cache/diagnostic files. ## Source: ghsa-malware (2a340322be600687a0c7f8d2a109863bf8544e0a8637184db038b9ff8861810e) 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:49:31 UTC
- Source modified
- 6 Aug 2026 01:20:29 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.