dolyame-boxy-atom-bnpl-cardnpm
dolyame-boxy-atom-bnpl-card is a confirmed malicious npm package (MAL-2026-13284) that executes malicious code on install (malicious version 35.5.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-boxy-atom-bnpl-card (npm)
What this malware does
On require of the package, index.js loads adapter.js, which downloads a platform-specific native binary from hardcoded destinations assembled via array-join concatenation (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) with a fallback that reassembles the executable from base64 chunks retrieved over DNS TXT records at c.dl.wel1.ru, sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under disguised names (dotnet_diag.exe,.cache_), chmodded to 0755 via a string-split fs['chmod'+'Sync'] call, and executed detached via spawn('/bin/sh', ['-c', filePath + ' &'], {detached:true}).unref() or a cmd equivalent on Windows. A ~24h marker file suppresses re-execution. A sibling lib/telemetry.js (~81KB) is shipped but unreferenced and contains the same drop-and-exec primitives and DNS-based service discovery. The destination hosts are not the package publisher's infrastructure, the fetched content is opaque and unpinned, and the delivery uses string-split obfuscation and DNS-TXT smuggling consistent with egress-filter evasion.
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-card (version 35.5.5). 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-card across your stack and pipelines.
If you installed it — respond
Remove dolyame-boxy-atom-bnpl-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-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-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-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.