NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bnpl-blocks-atom-bnpl-rangenpm

Advisory published Updated

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)

MAL-2026-12889
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-atom-bnpl-range

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

1 flagged
35.6.6

Indicators of compromise (SHA-256)

0d1d5c6a3a1bb7d8a26a77aada7abbec439922ebceec32b8608909ad2ee8acac

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-range (version 35.6.6).

  2. 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.

  3. Did it already run?

    If bnpl-blocks-atom-bnpl-range was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bnpl-blocks-atom-bnpl-range on npm has been identified as a malicious package (version 35.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015503

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
bnpl-blocks-atom-bnpl-range (npm) malicious package — MAL-2026-12889 | O3 Security