bnpl-blocks-desktop-bnpl-popupnpm
bnpl-blocks-desktop-bnpl-popup is a confirmed malicious npm package (MAL-2026-12937) that steals credentials and exfiltrates sensitive data (malicious version 35.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-popup (npm)
What this malware does
The package's main entry loads init.js on require. init.js selects a platform-specific URL, assembles C2 hostnames at runtime via string-split/join to evade static analysis (e.g. 'oob-worker.cf99-9b3.workers.dev' family, with a DNS TXT covert-channel fallback over *.dl.wel1.ru where 'c.<domain>' returns a chunk count and 'i.<domain>' returns base64-encoded payload chunks), downloads an opaque executable, writes it to /tmp or the Windows temp directory under a decoy name such as dotnet_diag<hex>.exe or.cache<hex>, chmods it 0755, and spawns it detached through /bin/sh -c or cmd.exe. Behavior is gated only by a stamp file and opt-out environment variables. The package presents itself as UI popup components, which has no legitimate reason to fetch and run a platform-specific binary from anonymous Cloudflare Workers endpoints at import time.
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-popup (version 35.9.9). 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-popup across your stack and pipelines.
If you installed it — respond
bnpl-blocks-desktop-bnpl-popup 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-popup 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-popup 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-popup-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.