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

bnpl-blocks-atom-bnpl-image-cardnpm

Advisory published Updated

bnpl-blocks-atom-bnpl-image-card is a confirmed malicious npm package (MAL-2026-13529) that typosquats a legitimate package to trick installs (malicious version 35.6.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-atom-bnpl-image-card (npm)

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

What this malware does

On require(), index.js loads bridge.js which selects a platform-specific asset path, fetches a binary over HTTPS from runtime-assembled Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT chunked-download fallback against wel1.ru subdomains, writes it to /var/tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or the Windows equivalent. Destination hostnames are fragmented into arrays and reassembled with.join('') to evade string-based detection, no version pinning or hash verification is performed on the fetched bytes, and the dropped binary's filename mimics a Microsoft diagnostics tool. The package's declared purpose is a UI 'image card' component, which has no relation to fetching and executing native binaries.

Malicious versions

1 flagged
35.6.1

Indicators of compromise (SHA-256)

abfb9fc4e628aff9ca7ab9df6b7a2b65c27eb1a094e4d64ff002a98f35eb58e1

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-image-card (version 35.6.1).

  2. If you installed it — respond

    bnpl-blocks-atom-bnpl-image-card is a typosquat — you almost certainly intended a legitimately-named package. Remove bnpl-blocks-atom-bnpl-image-card, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

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

Campaign

IN-MAL-2026-016967

References

Credits

  • Amazon Inspector · finder

Detect & block this

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