bnpl-blocks-desktop-bnpl-tablenpm
bnpl-blocks-desktop-bnpl-table is a confirmed malicious npm package (MAL-2026-12943) that steals credentials and exfiltrates sensitive data (malicious version 35.4.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-table (npm)
What this malware does
On require of the package, index.js unconditionally loads adapter.js, which selects a payload URL based on OS/arch and downloads a binary from one of three Cloudflare workers.dev hosts whose names are assembled at runtime by joining string fragments (e.g., ["oob-work","er.cf99-9b3",".w","or","kers",".dev"].join("")), with a DNS-TXT covert-channel fallback resolving through *.dl.wel1.ru. The downloaded bytes are written to a temp path under a deceptive name (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmod 0755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. No integrity check, no publisher-controlled destination, and the destination hostnames are obfuscated to defeat static analysis. Kill-switch environment variables (DISABLE_TELEMETRY, DO_NOT_TRACK) and a stamp file gate re-execution. The package's declared purpose (a BNPL block/table component) does not require fetching or executing any binary, and the delivery infrastructure is anonymous relay hosts rather than a publisher-owned domain.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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-table (version 35.4.7). 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-table across your stack and pipelines.
If you installed it — respond
bnpl-blocks-desktop-bnpl-table is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bnpl-blocks-desktop-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-desktop-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-desktop-bnpl-table-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.