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

bnpl-blocks-atom-bnpl-store-buttonnpm

Advisory published Updated

bnpl-blocks-atom-bnpl-store-button is a confirmed malicious npm package (MAL-2026-12896) that executes malicious code on install (malicious version 35.2.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-atom-bnpl-store-button (npm)

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

What this malware does

The package's main (index.js) requires ./_loader at module load, causing _loader.js to download a platform-specific native executable from hardcoded Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) whose hostnames are reassembled at runtime via Array.join string splitting to evade static scanners. If HTTPS fetches fail, a secondary channel retrieves base64-encoded chunks from DNS TXT records under *.dl.wel1.ru and reassembles them into the binary payload. The downloaded bytes are written to /tmp or %TEMP% under disguised filenames (.cache_<hex>, dotnet_diag_<hex>.exe), chmod'd to 0755 on Unix, and spawned detached via cp.spawn("/bin/sh", ["-c", fp + " &"]) or spawn("cmd",...) on Windows. No hash or signature verification is performed. Any require() or import of this package triggers full-host remote code execution. A second file, lib/telemetry.js, is not on the auto-executed graph in this version but contains structurally identical dropper primitives (base64 buffer to /bin/sh -c filePath &, chmod 0755, cp.spawn), mirroring the active loader.

Malicious versions

1 flagged
35.2.8

Indicators of compromise (SHA-256)

953b66d4203e461d482f00a2011c4d79b4fd30ab0749ca3e9946837d20e48504

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-store-button (version 35.2.8).

  2. If you installed it — respond

    Remove bnpl-blocks-atom-bnpl-store-button 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-store-button 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-store-button on npm has been identified as a malicious package (version 35.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015481

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-bnpl-store-button-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.

Explore

bnpl-blocks-atom-bnpl-store-button (npm) malicious package — MAL-2026-12896 | O3 Security