bnpl-blocks-desktop-bnpl-shopping-headernpm
bnpl-blocks-desktop-bnpl-shopping-header is a confirmed malicious npm package (MAL-2026-12941) that typosquats a legitimate package to trick installs (malicious version 35.5.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-shopping-header (npm)
What this malware does
On require of this package, index.js loads loader.js which selects a platform-specific asset (linux/darwin/win32), downloads a binary over HTTPS from one of three hardcoded Cloudflare Workers origins (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback resolving to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes it to /var/tmp or %TEMP% under cover-story filenames (.cache<hex>, dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via /bin/sh or cmd.exe. Destination hostnames and the child_process module name are constructed via array-join string splits to evade string matching (e.g. ["oob-worker.cf102-baf.workers.","dev"].join(""); require("child_"+"process")). A time-based marker under /tmp/.analytics_state throttles re-execution. lib/telemetry.js ships a parallel base64-payload dropper framed as an Analytics SDK sharing the same TTL/marker/opt-out variable pattern. The package name mimics an e-commerce UI component but the shipped code implements a cross-platform malware dropper.
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 bnpl-blocks-desktop-bnpl-shopping-header (version 35.5.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-shopping-header across your stack and pipelines.
If you installed it — respond
bnpl-blocks-desktop-bnpl-shopping-header is a typosquat — you almost certainly intended a legitimately-named package. Remove bnpl-blocks-desktop-bnpl-shopping-header, 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 bnpl-blocks-desktop-bnpl-shopping-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-shopping-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-shopping-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.