bnpl-blocks-atom-image-gallerynpm
bnpl-blocks-atom-image-gallery is a confirmed malicious npm package (MAL-2026-12905) that typosquats a legitimate package to trick installs (malicious version 35.2.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-image-gallery (npm)
What this malware does
On require() of the package, index.js loads setup.js which reconstructs attacker-controlled hostnames from split-string arrays (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev) with DNS TXT-record fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. setup.js downloads a platform-specific native executable, writes it to /tmp or the Windows Temp directory under diagnostics-mimicking filenames (dotnet_diag_<rand>.exe,.cache_<rand>), chmods 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd.exe. Platform-branched payload paths (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe) and opt-out env-var checks framed as 'telemetry' provide cover. A second bundled dropper in lib/telemetry.js (81KB) contains identical spawn+chmod+base64-DNS-decode logic with string-concatenated child_process import (require("child_" + "process")). The package advertises itself as image gallery components; there is no legitimate reason for such a package to download and execute native binaries at import time.
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-image-gallery (version 35.2.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-image-gallery across your stack and pipelines.
If you installed it — respond
bnpl-blocks-atom-image-gallery is a typosquat — you almost certainly intended a legitimately-named package. Remove bnpl-blocks-atom-image-gallery, 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-image-gallery 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-image-gallery 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-image-gallery-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.