Malicious code in dolyame-boxy-atom-bnpl-button (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-13283
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (963f070cd6563a11008f0726b4e0a11e5612dce9b53c58d9ea537566ab1774e2) On require, index.js loads _helpers.js which fetches a platform-specific binary from obfuscated hosts assembled via array-join (oob-worker.cf*.workers.dev) with a DNS-TXT chunked-base64 fallback channel to *.dl.wel1.ru, writes the bytes to /tmp/.cache_<rnd> or %TEMP%/dotnet_diag_<rnd>.exe, chmods 0755, and spawns the file detached via cp.spawn('/bin/sh',['-c', fp+' &'],{detached:true}) or cmd equivalent on Windows. No integrity or signature check is performed on the fetched bytes. Destination hostnames are string-split to evade static detection, and file/lock names (analytics_state, dotnet_diag_*.exe,.cache_*) plus code comments framing the spawn as 'Detached process to avoid blocking npm install' present the behavior as telemetry. A lockfile with a ~22000s max age throttles re-fetching into a scheduled beacon pattern. The DNS-TXT channel provides a covert payload path when HTTPS egress is blocked. Any installer requiring this package executes attacker-controlled arbitrary code on their host. ## Source: ghsa-malware (4fcffe6de0ccd3c2c780baeec4bc4617727847bcd6170d0bd92d067abc3fade4) 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:29:42 UTC
- Source modified
- 6 Aug 2026 01:20:42 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.