bnpl-blocks-desktop-bnpl-header-searchnpm
bnpl-blocks-desktop-bnpl-header-search is a confirmed malicious npm package (MAL-2026-12927) that executes malicious code on install (malicious version 35.2.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-header-search (npm)
What this malware does
On require of the package, index.js loads adapter.js whose top-level main() constructs Cloudflare Workers hostnames (oob-worker.cf10{0-3}-.workers.dev) and a DNS-TXT discovery fallback (.dl.wel1.ru) via array-join string splitting, downloads a platform-specific binary, writes it to a temp path under disguised OS-diagnostic filenames (dotnet_diag.exe /.cache_), chmods it 0755, and spawns it detached via spawn("/bin/sh",["-c", filePath+" &"]) or cmd /c start /b. A second variant of the same drop/chmod/spawn chain is present in lib/telemetry.js, using Buffer.from(chunks,"base64") to reconstruct payload bytes. The package presents itself as an analytics/telemetry component (stamp file.analytics_state, DISABLE_TELEMETRY opt-out shim) but its declared purpose is a BNPL header-search UI block, which has no legitimate need to execute unsigned remote binaries. The endpoint obfuscation, cover-story naming, DNS-TXT censorship-evasion fallback, and disguised on-disk artifacts are characteristic of a hostile dropper.
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 bnpl-blocks-desktop-bnpl-header-search (version 35.2.6). 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-search across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-desktop-bnpl-header-search 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 bnpl-blocks-desktop-bnpl-header-search 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-search 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-search-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.