dolyame-boxy-independent-bnpl-scheme (npm) · Malicious Code
Affects dolyame-boxy-independent-bnpl-schemeSource GCVE Database
Malicious package : remove dolyame-boxy-independent-bnpl-scheme and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-13327
What to do
Remove dolyame-boxy-independent-bnpl-scheme from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmdolyame-boxy-independent-bnpl-scheme | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (bce523b3385816616192d462b5ac251d22886682d021200c4bd76bd22b95003c) On require of this package, index.js loads setup.js which downloads a platform-specific native binary from author-controlled Cloudflare Workers hosts (with a DNS TXT fallback via sdk.dl.wel1.ru), writes it to /var/tmp or %TEMP% under disguised filenames (.cache_<hex>, dotnet_diag_<hex>.exe), chmods it to 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are reconstructed from array-joined string fragments (e.g. ['oob-worker','.cf10','1-adf.w','ork','ers.d','ev'].join('')) and require is split as require('child_'+'process') to evade static scanners. Execution is gated by a lockfile cooldown to run once per host. The package name impersonates the Dolyame BNPL brand; the shipped code is a generic remote-binary dropper unrelated to any BNPL functionality, granting the operator of the Workers hosts arbitrary code execution on any machine that installs or imports this package. ## Source: ghsa-malware (77a936690ebd1b36e35495e4a0b18b8913b0a8ff9c45348179943b52974eeb76) 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.