dolyame-boxy-atom-bnpl-image-cardnpm
dolyame-boxy-atom-bnpl-image-card is a confirmed malicious npm package (MAL-2026-13287) that executes malicious code on install (malicious version 35.7.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-boxy-atom-bnpl-image-card (npm)
What this malware does
The package's main entry loads setup.js, which on require() fetches a platform-specific binary from Cloudflare Workers subdomains whose hostnames are reconstructed at runtime via array.join() (e.g. ['oob-worker.cf10','2-baf.w','orker','s.dev'].join('')) to evade static inspection. A DNS-TXT fallback channel under .dl.wel1.ru retrieves base64-encoded chunks (count via c.<domain>, chunks via <i>.<domain>) that are concatenated and decoded. The retrieved binary is written to /tmp or %TEMP% under cover-story names (.cache_, dotnet_diag_*.exe), chmod 755'd on POSIX via a split fs['chmod'+'Sync'] call, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}).unref() (or cmd on Windows). No lifecycle hook is required; any consumer that imports the package triggers execution. A sibling lib/telemetry.js, framed as an 'Analytics SDK' and not wired in, contains the same dropper primitives (split require('child_'+'process'), split chmodSync, base64 chunk assembly, detached /bin/sh spawn), indicating a shared dropper family.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-boxy-atom-bnpl-image-card (version 35.7.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-atom-bnpl-image-card across your stack and pipelines.
If you installed it — respond
Remove dolyame-boxy-atom-bnpl-image-card from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dolyame-boxy-atom-bnpl-image-card was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dolyame-boxy-atom-bnpl-image-card before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dolyame-boxy-atom-bnpl-image-card-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.