dolyame-boxy-atom-bnpl-email-form (npm) · Malicious Code
Affects dolyame-boxy-atom-bnpl-email-formSource GCVE Database
Malicious package : remove dolyame-boxy-atom-bnpl-email-form 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-12363
What to do
Remove dolyame-boxy-atom-bnpl-email-form 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-atom-bnpl-email-form | 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 (8e9cb745c0771868eb6908cf1c783614da3e41fe1d1cf52b4d2d04705c51af19) On require of the package's main, index.js side-loads _runtime.js which selects a per-platform payload path, fetches an opaque binary from string-split obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to /var/tmp or %TEMP% with a disguised filename (`.cache_<hex>`, `dotnet_diag_<hex>.exe`, `.analytics_state`), chmods 0755, and spawns it detached via child_process.spawn('/bin/sh') or spawn('cmd'). When the HTTPS mirrors fail, _runtime.js falls back to a DNS TXT covert channel: it resolves `c.<domain>` for a chunk count, iterates `<i>.dl.well1.site` TXT records (tin/tina/ldr/win subdomains), concatenates and base64-decodes them into the payload, then writes and spawns it. Host names, fallback DNS domains, and the string 'child_process' are assembled from split string arrays at runtime to evade static analysis. There is no version pinning, hash check, or signature verification, and the destinations are not the publisher's infrastructure. Cover-story framing as an 'Analytics SDK' with a DISABLE_TELEMETRY opt-out does not match the actual fetch-decode-write-chmod-spawn behavior. ## Source: ghsa-malware (e476a87c0e4538a947633f4bd6a61d856208adab0161811adf5ae087c9b02915) 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.