dolyame-boxy-independent-bnpl-itemsnpm
dolyame-boxy-independent-bnpl-items is a confirmed malicious npm package (MAL-2026-13319) that typosquats a legitimate package to trick installs (malicious version 35.3.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dolyame-boxy-independent-bnpl-items (npm)
What this malware does
On require() of this package, index.js loads compat.js which unconditionally downloads an OS-specific binary from Cloudflare Workers hosts assembled at runtime via string-array join (oob-worker.cf99-9b3.workers.dev, cf100-416.workers.dev, cf102-baf.workers.dev, cf103-070.workers.dev), with a DNS-TXT chunked fallback served under *.dl.wel1.ru (sdk.dl.wel1.ru). The fetched bytes are written to /tmp or %TEMP% under cover-story filenames (analytics_state, dotnet_diag.exe,.cache_), chmod 0755 on POSIX, then spawned detached and unref'd via /bin/sh -c or cmd.exe /c start /b. No hash or signature verification, no relationship to any legitimate publisher, and the hostnames and the child_process require are obfuscated via array.join to defeat static analysis. Package name impersonates a Dolyame BNPL integration but ships no such functionality.
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
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dolyame-boxy-independent-bnpl-items (version 35.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dolyame-boxy-independent-bnpl-items across your stack and pipelines.
If you installed it — respond
dolyame-boxy-independent-bnpl-items is a typosquat — you almost certainly intended a legitimately-named package. Remove dolyame-boxy-independent-bnpl-items, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dolyame-boxy-independent-bnpl-items 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-independent-bnpl-items 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-independent-bnpl-items-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.