bnpl-blocks-atom-bnpl-dangerously-htmlnpm
bnpl-blocks-atom-bnpl-dangerously-html is a confirmed malicious npm package (MAL-2026-12870) that opens a backdoor for remote access (malicious version 35.2.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-dangerously-html (npm)
What this malware does
On any require() of this package, index.js loads compat.js which unconditionally downloads a platform-specific binary from hardcoded Cloudflare Workers (oob-worker.cf101-.workers.dev, oob-worker.cf102-.workers.dev, oob-worker.cf99-9b3.workers.dev) and *.dl.wel1.ru hosts (sdk, ext, pkg, net subdomains), with a DNS-TXT base64 fallback channel (c.<domain>, 0.<domain>, 1.<domain>... TXT records reassembled and base64-decoded). Destination hostnames are assembled at runtime from split-string fragments joined together to evade static analysis. The downloaded binary is written to /var/tmp or the OS temp directory under disguising names (.cache<hex>, dotnet_diag_<hex>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd /c start /b. The package name references legitimate BNPL block terminology as cover; the actual behavior is a load-time binary dropper with obfuscated multi-channel C2.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-atom-bnpl-dangerously-html (version 35.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-bnpl-dangerously-html across your stack and pipelines.
If you installed it — respond
bnpl-blocks-atom-bnpl-dangerously-html establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bnpl-blocks-atom-bnpl-dangerously-html 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 bnpl-blocks-atom-bnpl-dangerously-html 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 bnpl-blocks-atom-bnpl-dangerously-html-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.