dolyame-boxy-independent-bnpl-code-text (npm) · Malicious Code
Affects dolyame-boxy-independent-bnpl-code-textSource GCVE Database
Malicious package : remove dolyame-boxy-independent-bnpl-code-text 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-13315
What to do
Remove dolyame-boxy-independent-bnpl-code-text 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-code-text | 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 (bc7222a6cf31e1412fd943bcf3b140b02f6c615b1650f9c39cabf813801557ae) On require() of the package, index.js loads _ext.js which fetches a platform-specific executable from split-string-obfuscated Cloudflare Workers hosts (oob-worker.cf*.workers.dev) with a DNS-TXT covert-channel fallback under *.dl.wel1.ru (c.<domain> for chunk count, i.<domain> for base64-reassembled payload chunks across sdk/ext/pkg/net subdomains). The fetched bytes are written to /tmp or %TEMP% under a disguised name (dotnet_diag_<hex>.exe /.cache_<hex>), chmod 755'd, and spawned detached via /bin/sh -c or cmd /c start. Destination hostnames are reconstructed via array-join to evade static string scanning. The behavior is framed as opt-out telemetry (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env checks,.analytics_state file), and lib/telemetry.js contains a parallel Buffer.from(chunks,'base64') + fs.chmodSync + cp.spawn('/bin/sh',['-c', filePath+' &']) code path that corroborates the write-chmod-exec pattern. ## Source: ghsa-malware (f19d34835a9a9239da98c35195bbeefb0f0b5f67e698897c2730cdf4b8262b90) 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.