bnpl-blocks-mobile-bnpl-tablenpm
bnpl-blocks-mobile-bnpl-table is a confirmed malicious npm package (MAL-2026-13008) that executes malicious code on install (malicious version 35.1.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-table (npm)
What this malware does
On require of this package, main resolves to _runtime.js, which assembles Cloudflare Workers hostnames by string-splitting (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) and falls back to DNS TXT record retrieval under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru. The fetched platform-specific binary is written to /var/tmp/.cache_<hex> on Linux or %TEMP%\dotnet_diag_<hex>.exe on Windows, marked executable via fs.chmodSync(..., 0o755), and spawned detached through /bin/sh -c '<path> &' or cmd.exe /c start /b, with the child_process require and chmodSync call assembled by string concatenation to evade static matching. A second module, lib/telemetry.js (~80KB), is framed as an analytics SDK and duplicates the same write+chmod+spawn dropper primitives with identical string-split obfuscation; it is not reached from the current entrypoint but is present in the tarball as a dormant second stage. Cover filenames imitating cache and.NET diagnostic files, an environment-variable opt-out framed as a cover story, and rate-limiting all indicate deliberate concealment.
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-table (version 35.1.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-table across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-bnpl-table 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-table 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-table 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-table-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.