bnpl-blocks-desktop-bnpl-headernpm
bnpl-blocks-desktop-bnpl-header is a confirmed malicious npm package (MAL-2026-12925) that opens a backdoor for remote access (malicious version 35.7.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-header (npm)
What this malware does
On require() of this package, index.js loads bridge.js, which reconstructs C2 hostnames from split string fragments (e.g. ["oob-worker",".cf","10","3-070.worke","rs.d","ev"].join("")) to resolve oob-worker.cf*.workers.dev endpoints and a DNS-TXT fallback under *.dl.wel1.ru. It downloads a platform-specific binary (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), writes it to /var/tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh or cmd.exe /c start /b, using a marker file to suppress repeat execution. A DNS-TXT channel reassembles base64 chunks from sequentially numbered TXT records as a fallback. Cover strings referencing analytics/telemetry/dotnet_diag are misdirection; the destinations are non-publisher, anonymous Cloudflare Workers and Russian DNS hosts, and the fetched bytes are opaque binaries executed on the installer's host. An additional 81 KB lib/telemetry.js is shipped but not reached from index.js or _bridge.js.
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-desktop-bnpl-header (version 35.7.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-desktop-bnpl-header across your stack and pipelines.
If you installed it — respond
bnpl-blocks-desktop-bnpl-header 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-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 bnpl-blocks-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 bnpl-blocks-desktop-bnpl-header-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.