bnpl-blocks-atom-bnpl-image-cardnpm
bnpl-blocks-atom-bnpl-image-card is a confirmed malicious npm package (MAL-2026-13529) that typosquats a legitimate package to trick installs (malicious version 35.6.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-image-card (npm)
What this malware does
On require(), index.js loads bridge.js which selects a platform-specific asset path, fetches a binary over HTTPS from runtime-assembled Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT chunked-download fallback against wel1.ru subdomains, writes it to /var/tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or the Windows equivalent. Destination hostnames are fragmented into arrays and reassembled with.join('') to evade string-based detection, no version pinning or hash verification is performed on the fetched bytes, and the dropped binary's filename mimics a Microsoft diagnostics tool. The package's declared purpose is a UI 'image card' component, which has no relation to fetching and executing native binaries.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind 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-image-card (version 35.6.1). 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-image-card across your stack and pipelines.
If you installed it — respond
bnpl-blocks-atom-bnpl-image-card is a typosquat — you almost certainly intended a legitimately-named package. Remove bnpl-blocks-atom-bnpl-image-card, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bnpl-blocks-atom-bnpl-image-card 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-image-card 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-image-card-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.