bnpl-blocks-atom-bnpl-popupnpm
bnpl-blocks-atom-bnpl-popup is a confirmed malicious npm package (MAL-2026-12885) that executes malicious code on install (malicious version 35.4.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-popup (npm)
What this malware does
On require() of this package, index.js loads shim.js which assembles obfuscated non-publisher URLs by joining split string fragments (resolving to a *.workers.dev host, with a DNS-TXT covert-channel fallback under a.ru domain that reconstructs a payload from base64-encoded TXT records at c.<domain> and <i>.<domain>). shim.js downloads a platform-specific binary, writes it to /tmp or %TEMP% under a disguised filename (.cache<hex> on Unix, dotnet_diag<hex>.exe on Windows), chmods 0755, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp+' &'], {detached:true}).unref() (or the cmd equivalent). No hash or signature verification is performed. A second copy of the dropper is shipped in lib/telemetry.js (labeled as an 'Analytics SDK') using the same shape with split-string API names such as require('child_'+'process') and fs['chmod'+'Sync']; it is not wired into the current entry point but stages the same capability. The destination hosts are not first-party to the package, and the string-splitting plus DNS-TXT channel are anti-analysis tradecraft rather than legitimate telemetry configuration.
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-popup (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-atom-bnpl-popup across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-popup 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-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-atom-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-atom-bnpl-popup-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.