dolyame-boxy-desktop-bnpl-headernpm
dolyame-boxy-desktop-bnpl-header is a confirmed malicious npm package (MAL-2026-13304) that executes malicious code on install (malicious version 35.8.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-boxy-desktop-bnpl-header (npm)
What this malware does
On require of the package, index.js unconditionally loads bootstrap.js, which downloads a platform-specific binary from hostnames assembled via split-string concatenation (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with fallbacks to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru and a DNS TXT-record base64-chunk retrieval channel. The downloaded binary is written to /tmp or %TEMP% under a decoy hidden filename (.cache<uid>, dotnet_diag_<uid>.exe), chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Hostnames and API names are runtime-assembled ("child_"+"process", "chmod"+"Sync") to defeat static scanners. A second, larger implementation of the same drop-and-exec pattern is shipped as lib/telemetry.js under an 'analytics SDK' cover story.
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-desktop-bnpl-header (version 35.8.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-desktop-bnpl-header across your stack and pipelines.
If you installed it — respond
Remove dolyame-boxy-desktop-bnpl-header 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-desktop-bnpl-header 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-desktop-bnpl-header 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-desktop-bnpl-header-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.