bnpl-blocks-mobile-bnpl-text-blocknpm
bnpl-blocks-mobile-bnpl-text-block is a confirmed malicious npm package (MAL-2026-13009) that executes malicious code on install (malicious version 35.2.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-text-block (npm)
What this malware does
On require of index.js, support.js unconditionally executes a dropper routine: it HTTPS-fetches an opaque binary from hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT fallback under *.dl.wel1.ru, writes the response to a temp path using masquerading filenames (.cache, dotnet_diag_.exe), chmods it to 0755, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}). Destination hostnames are assembled at runtime by array-join (e.g., ["oob-worker.cf102-baf",".wo","rke","rs.de","v"].join("")) and require("child_"+"process") is used to evade static scanners. A second bundled module lib/telemetry.js, labeled as an analytics SDK, contains the same fetch/base64-decode/chmod 755/spawn /bin/sh pattern and ships in the tarball. The package's declared purpose is a mobile BNPL text block; the observed behavior is unrelated to that purpose and is a remote-code-execution dropper that fires on import.
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-text-block (version 35.2.2). 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-text-block across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-bnpl-text-block 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-text-block 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-text-block 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-text-block-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.