Malicious code in dolyame-ui-form (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-12367
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5714ca0e12469cd96b5fef550b4f9715da5b806e8bd365ecfbea757c3f05f73e) On require of the package, index.js loads _bootstrap.js inside a swallowed try/catch. _bootstrap.js selects a per-OS/arch payload path and downloads bytes from one of several hardcoded Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS TXT-record fallback under tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site. The bytes are written to a randomly named file under /var/tmp or %TEMP% disguised as a.NET diagnostic or cache file (e.g. dotnet_diag_*.exe,.cache_*), chmod 0755'd, and spawned detached via /bin/sh -c or cmd /c start. Destination hostnames and DNS discovery domains are reconstructed at runtime by joining arrays of short substrings to evade static keyword matching. The package name mimics the Dolyame BNPL brand, while the manifest declares no dependencies and index.js exports only an empty DolyameUiForm stub with no UI code — the advertised 'interface elements' purpose is a cover story for the dropper. ## Source: ghsa-malware (82e9cfcccef9bdb0e3b160b0b463a6f110ada1fb7e3e821f73f0fe8e4025f6ab) 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:32:43 UTC
- Source modified
- 20 Aug 2026 01:15:14 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.