bnpl-blocks-mobile-bnpl-titlenpm
bnpl-blocks-mobile-bnpl-title is a confirmed malicious npm package (MAL-2026-13010) that executes malicious code on install (malicious version 35.7.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-title (npm)
What this malware does
On require of the package, index.js loads support.js, which selects a per-platform binary path, downloads bytes from a pool of obfuscated Cloudflare Workers mirrors whose hostnames are reassembled at runtime from split string fragments (e.g. oob-worker.cf103-070.workers.dev), writes the payload to a disguised temp filename such as dotnet_diag<hex>.exe or.cache_<hex>, chmods 0755 on POSIX, and spawns it detached via cmd.exe /c start /b or /bin/sh -c '<path> &'. If HTTPS mirrors fail, a fallback covert channel resolves DNS TXT records under *.dl.wel1.ru, reassembles a base64-encoded executable from chunked TXT responses, and executes it the same way. No hash or signature check is performed. Hostnames are hidden via split-and-join to evade static inspection. The combination of import-time execution, unpinned remote payload, non-publisher hosts with obfuscated names, DNS-over-TXT payload transport, and detached background spawn is a full-host remote code execution channel against the installer.
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-mobile-bnpl-title (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-mobile-bnpl-title across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-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-mobile-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-mobile-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-mobile-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.