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

bnpl-blocks-atom-bnpl-badgenpm

Advisory published Updated

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

Malicious code in bnpl-blocks-atom-bnpl-badge (npm)

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

What this malware does

On require of the package, index.js unconditionally loads polyfill.js, which downloads a platform-specific binary from one of three obfuscated Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT base64-chunk fallback under *.wel1.ru, writes it to a hidden file in /tmp or %TEMP% (e.g..cache<hex>, dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. Destination hostnames and DNS domains are reconstructed at runtime by Array.join to evade static string matching. A sibling module lib/telemetry.js (~81 KB) contains the same dropper primitives (base64 chunk decoding, cp.spawn('/bin/sh',...), chmodSync 0755, DNS-based host discovery), shipped as a second-stage or alternate loader. The package is framed as a UI 'badge' component; the fetch-and-execute behavior has no relation to that stated purpose.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
35.6.8

Indicators of compromise (SHA-256)

e57d88037b98733cb7376fa7fa11e80d1d6eb6f9373a7d6e1b555e96039b3abe
839ef9ca6d27bc1d0636fec594fb361bcbc71e30148baaf6c5d90da4cd133d69

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-badge (version 35.6.8).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015512GHSA-6hgf-fq2c-gw65

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-bnpl-badge-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-badge (npm) malicious package — MAL-2026-12864 | O3 Security