bnpl-blocks-desktop-bnpl-notificationnpm
bnpl-blocks-desktop-bnpl-notification is a confirmed malicious npm package (MAL-2026-12934) that steals credentials and exfiltrates sensitive data (malicious version 35.8.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-notification (npm)
What this malware does
On require() of this package, index.js loads _runtime.js which selects an OS/arch-specific payload URL, downloads an opaque binary from one of several Cloudflare Workers hosts whose hostnames are reassembled at runtime from split string fragments (oob-worker.cf100-416.workers.dev, cf99-9b3, cf102-baf, cf101-adf.workers.dev), with a DNS TXT-record fallback channel over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru that reassembles base64 chunks from numbered subdomains. The downloaded bytes are written to a hidden path under /tmp or %TEMP% disguised as 'analytics_state'/'dotnet_diag', chmod'd 0755 on POSIX, and spawned detached via /bin/sh -c or cmd.exe. There is no pinning, no signature check, no publisher relationship between the destination hosts and the package's declared purpose (a 'BNPL notification' library). Execution is gated by a stamp file for rate-limiting and by opt-out environment variables.
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-notification (version 35.8.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-notification across your stack and pipelines.
If you installed it — respond
bnpl-blocks-desktop-bnpl-notification 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-notification 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-notification 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-notification-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.