bnpl-blocks-atom-containernpm
bnpl-blocks-atom-container is a confirmed malicious npm package (MAL-2026-12900) that executes malicious code on install (malicious version 35.7.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-container (npm)
What this malware does
On require() of bnpl-blocks-atom-container, index.js loads adapter.js which selects a platform-specific target path, downloads an opaque binary from one of four Cloudflare Workers hosts whose names are reconstructed at runtime from split string fragments (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), writes it to /var/tmp or %TEMP% under cover-story filenames ('dotnet_diag<hex>.exe' on Windows, '.cache_<hex>' on Unix), chmods 0755, and spawns it detached via '/bin/sh -c <fp> &' or 'cmd.exe /c start /b <fp>'. A stamp file named '.analytics_state' under /tmp gates re-execution. When HTTPS delivery fails, the loader falls back to a DNS-over-TXT channel against *.dl.wel1.ru (sdk./ext./pkg./net.dl.wel1.ru): it reads a chunk count from a 'c.<domain>' TXT record, retrieves N indexed base64 TXT records, concatenates and base64-decodes them into the payload bytes, and executes the result. Hostname obfuscation, disguised staging filenames, and a redundant covert DNS delivery channel are consistent with evasion of both static scanners and HTTP egress controls, not with any legitimate SDK loader.
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-container (version 35.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-container across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-container 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-container 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-container 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-container-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.