Malicious code in devplatform-nx-react (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-12726
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9293216b770bf95ede58df5d7aee19ded2826ca8fc027b44896474319483bb07) The package advertises itself as 'reusable nx react components' but its index.js unconditionally requires _support.js, which fetches and executes an attacker-controlled binary on load. Hostnames are assembled at runtime from split character arrays to evade static analysis: HTTPS mirrors resolve to oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, and oob-worker.cf103-070.workers.dev on Cloudflare Workers, with a DNS-TXT chunked fallback against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru (a count is read from c.<domain>, then N base64 TXT chunks are reassembled into an executable). The downloaded payload is written to a temp path with a randomized name, chmodded 0755, and spawned detached via `spawn('/bin/sh', ['-c', fp+' &'])` on Unix or `cmd.exe /c start /b fp` on Windows. Comments and identifiers ('analytics_state', 'dotnet_diag_', 'telemetry', 'Cross-platform path resolution') act as cover for the loader. The dropper has no relation to the package's stated purpose, and no integrity check, pinning, or publisher-controlled source is present. ## Source: ghsa-malware (fbd835a40a29c30efae55e501f7cd7996179a8f41f2ec1ed67560580bc67a4a3) 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:57 UTC
- Source modified
- 6 Aug 2026 01:20:30 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.