bnpl-blocks-desktop-bnpl-card-panelnpm
bnpl-blocks-desktop-bnpl-card-panel is a confirmed malicious npm package (MAL-2026-12917) that executes malicious code on install (malicious version 35.9.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-card-panel (npm)
What this malware does
On require, index.js loads polyfill.js which selects a platform-specific payload path, downloads bytes over HTTPS from string-split-obfuscated Cloudflare workers.dev hostnames (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT chunked base64 fallback over sdk.dl.wel1.ru, writes the bytes to a temp file under a decoy name (dotnet_diag.exe /.cache_), chmods it 0755, and spawns it detached via cmd.exe or /bin/sh. There is no version pin, no hash check, and no signature verification. Destination hostnames are assembled by concatenating string fragments (e.g. ["oob-worker.cf101-adf.workers.","de","v"].join("")) and a DNS-TXT covert-channel fallback (resolveTxt("c."+domain) + base64 decode) is implemented to survive HTTPS egress blocking. The child_process spawn of a downloaded binary confirms code execution, not telemetry.
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-desktop-bnpl-card-panel (version 35.9.2). 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-card-panel across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-desktop-bnpl-card-panel 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-desktop-bnpl-card-panel 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-card-panel 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-card-panel-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.