dolyame-boxy-independent-bnpl-button (npm) · Malicious Code
Affects dolyame-boxy-independent-bnpl-buttonSource GCVE Database
Malicious package : remove dolyame-boxy-independent-bnpl-button 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-13313
What to do
Remove dolyame-boxy-independent-bnpl-button 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-button | 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 (cfda80d3053a8c106f2665b5c1a9a9235532a4acca7abd2a436b5c69fe7673d6) On require() of the package's main entry, _runtime.js fetches an opaque native binary from anonymous Cloudflare workers.dev subdomains (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT chunked fallback resolving hosts under dl.wel1.ru (sdk./ext./pkg./net.), writes it to /var/tmp/.cache_<hex> or %TEMP%/dotnet_diag_<hex>.exe, chmods 0755, and spawns it detached via /bin/sh -c... & or cmd /c start. Hostnames are assembled at runtime from split-string arrays and child_process is loaded via a runtime require() inside _activate(), consistent with static-scanner evasion. Filenames masquerade as dotnet_diag /.cache and a TTL marker (analytics_state) rate-limits re-execution. Installing or requiring this package yields full-host code execution on the installer under attacker-controlled bytes. ## Source: ghsa-malware (20ea76efd9c7012010991937c1135b107f66754480f47907e869438deeee3bed) 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.