bnpl-blocks-atom-bnpl-rangenpm
bnpl-blocks-atom-bnpl-range is a confirmed malicious npm package (MAL-2026-12889) that executes malicious code on install (malicious version 35.6.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-range (npm)
What this malware does
On require of index.js, shim.js executes immediately and fetches an opaque binary from one of three string-concatenation-obfuscated origins (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS TXT fallback under *.dl.wel1.ru. The fetched bytes are written to /tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<uid>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c or cmd. No hash or signature verification is performed. Hostnames, the DNS resolver domain, and the child_process module name are assembled at runtime via array-join concatenation to evade static analysis. The package name/version, masqueraded staging filename (dotnet_diag), dotfile staging path, and covert DNS-TXT fallback channel are consistent with a targeted supply-chain dropper.
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-range (version 35.6.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-bnpl-range across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-range 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-range 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-range 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-range-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.