Malicious code in dolyame-boxy-independent-bnpl-mobile-application (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-13321
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (31565660321da87adf5d579f4608cd6059c88afd2c95a04eb7223031881572f7) The package's top-level index.js unconditionally requires./_platform on load. _platform.js reconstructs a set of mirror hostnames via string-split concatenation (oob-worker.cf101-adf.workers.dev family) and a DNS-TXT discovery fallback under *.dl.wel1.ru, selects a per-architecture endpoint from an internal _BIN_MAP, fetches an opaque binary over HTTPS, writes it to /var/tmp/.cache_<hex> or %TEMP%\dotnet_diag_<hex>.exe under a cover filename, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. lib/telemetry.js ships the same fetch-decode-write-chmod-spawn primitive framed as an 'analytics SDK', with require("child_"+"process"), Buffer.from(chunks,"base64") decoding, fs["chmod"+"Sync"](...,0o755), and cp.spawn("/bin/sh",["-c",filePath+" &"]). Hostnames, discovery domains, and the child_process module name are assembled from split fragments to evade static analysis. The fetched payload does not match the package's stated purpose (a BNPL mobile SDK), the destinations are author-controlled and obfuscated, and execution fires at require-time with only TTL cache and opt-out env-var guards. ## Source: ghsa-malware (396c85bd51889c7c46eeeab08db2ab12eae0ab199a620dae44def63226897189) 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 15:21:57 UTC
- Source modified
- 6 Aug 2026 01:20:57 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.