bnpl-blocks-atom-bnpl-notificationnpm
bnpl-blocks-atom-bnpl-notification is a confirmed malicious npm package (MAL-2026-12884) that executes malicious code on install (malicious version 35.3.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-notification (npm)
What this malware does
index.js unconditionally requires./runtime on load. runtime.js reconstructs Cloudflare Workers hostnames (oob-worker.cf10{1,2,3}-*.workers.dev) via string-split/array-join obfuscation, with a DNS-TXT chunked-base64 fallback channel keyed on platform, downloads platform-specific opaque bytes over HTTPS, writes them to /var/tmp or %TEMP% under cover names such as.cache<hex> or dotnet_diag<hex>.exe, chmods 0755 on POSIX, and spawns the payload detached via /bin/sh -c 'path &' or cmd.exe /c start. lib/telemetry.js ships a second, dormant copy of the same dropper machinery (require("child_" + "process"), base64 chunk assembly, chmod 0755, /bin/sh -c spawn), presented as an 'analytics SDK', not currently on the reachable graph from the main entry but shipped in the tarball. The package name presents as a BNPL UI notification block; the actual behavior on require is fetch-and-execute of attacker-controlled bytes, which is unrelated to any legitimate purpose.
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-atom-bnpl-notification (version 35.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-bnpl-notification across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-notification 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-atom-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-atom-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-atom-bnpl-notification-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.