bnpl-blocks-desktop-bnpl-titlenpm
bnpl-blocks-desktop-bnpl-title is a confirmed malicious npm package (MAL-2026-12945) that executes malicious code on install (malicious version 35.7.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-title (npm)
What this malware does
The package's main entry (index.js) requires support.js on load. support.js selects a platform-specific path, then downloads a binary over HTTPS from Cloudflare Worker hostnames that are reconstructed at runtime by joining split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev). If HTTPS retrieval fails, a fallback channel uses DNS TXT queries against *.dl.wel1.ru (c.<domain> for chunk count, i.<domain> for base64-encoded chunks) to reassemble the payload out-of-band. The downloaded bytes are written to /var/tmp or %TEMP% under deceptive names such as dotnet_diag<rand>.exe and.cache<rand>, chmod'd 0755, and executed detached via /bin/sh -c "<path> &" or cmd.exe /c start. No hash or signature verification is performed. The advertised purpose ("bnpl title provider") has no relation to any of this behavior. A second file, lib/telemetry.js, is not currently required but contains structurally identical dropper primitives (base64 payload assembly, chmod 0755 via bracket-split property name, /bin/sh detached spawn of a downloaded file), staged for activation by a one-line require change.
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-title (version 35.7.9). 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-title across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-desktop-bnpl-title 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-title 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-title 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-title-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.