bnpl-blocks-mobile-bnpl-anchor-titlenpm
bnpl-blocks-mobile-bnpl-anchor-title is a confirmed malicious npm package (MAL-2026-12978) that executes malicious code on install (malicious version 35.8.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-anchor-title (npm)
What this malware does
On require() of the package's main entry, index.js loads platform.js which fetches a platform-specific binary from Cloudflare Workers hostnames (oob-worker.cf*.workers.dev) reconstructed via.join('') from split string fragments, with a DNS-TXT record fallback channel (c.<domain> count + numbered TXT records reassembled from base64) pointing at *.dl.wel1.ru to bypass HTTP egress filtering. The fetched bytes are written to /var/tmp or %TEMP% under cover-story names (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmod 0755 on Unix, and spawned detached via spawn('/bin/sh',...) or spawn('cmd', ['/c', 'start',...]). A TTL marker file suppresses re-runs. Hosts are not publisher-controlled, unrelated to any documented package purpose, and no hash/signature verification is performed. A second dropper variant with the same shape is present in lib/telemetry.js wrapped as a fake analytics SDK; it is not reachable from index.js in this version.
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-anchor-title (version 35.8.3). 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-anchor-title across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-bnpl-anchor-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-anchor-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-anchor-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-anchor-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.