dolyame-boxy-atom-bnpl-info-card (npm) · Malicious Code
Affects dolyame-boxy-atom-bnpl-info-cardSource GCVE Database
Malicious package : remove dolyame-boxy-atom-bnpl-info-card 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-13288
What to do
Remove dolyame-boxy-atom-bnpl-info-card 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-info-card | 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 (abfa5d8518650ddd83b31e9587264a2ed049a47db5c8452af6d62eb50e9fa336) On load, index.js requires./_loader.js which reconstructs anonymous host names via array-join obfuscation (['oob-worker.cf100-416.work','ers.','dev'].join('') and ['sdk.dl.wel','1.','ru'].join('')), selects a platform-specific payload path, downloads an opaque binary from those hosts with a DNS-TXT fallback via *.dl.wel1.ru, writes it to /var/tmp/.cache_<hex> on Unix or TEMP\dotnet_diag_<hex>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd. A marker file gates re-runs and env-var checks provide a cover-story opt-out. lib/telemetry.js repeats the same shape using string-concatenation obfuscation for require('child_'+'process') and fs['chmod'+'Sync']. No hash or signature verification is performed; the destinations are anonymous, mutable CDN hosts unrelated to any declared purpose. Filename shape (dolyame-boxy-atom-bnpl-info-card) is also consistent with a lookalike/lure name. ## Source: ghsa-malware (600a1ec6272503e4b2b7e2c31a33b996c07fb5eb543a5169c483ea1e7cef7a67) 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.