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

bnpl-blocks-desktop-bnpl-header-catalognpm

Advisory published Updated

bnpl-blocks-desktop-bnpl-header-catalog is a confirmed malicious npm package (MAL-2026-12926) that executes malicious code on install (malicious version 35.3.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-desktop-bnpl-header-catalog (npm)

MAL-2026-12926
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-desktop-bnpl-header-catalog

What this malware does

The package presents itself as a 'logging middleware' but its index.js unconditionally requires loader.js on module load. loader.js selects a per-OS asset and fetches it over HTTPS from a randomized list of anonymous Cloudflare Workers hostnames (reconstructed via split-string concatenation such as ["oob-wor","ker.cf100-416.workers",".de","v"].join("")). If HTTPS fails, it falls back to a DNS TXT covert channel that queries c.<host> then sequential numeric subdomains under *.dl.wel1.ru, concatenates the TXT chunks, and base64-decodes them into an executable payload. The fetched bytes are written to a disguised path under /var/tmp or %TEMP% (e.g. dotnet_diag*.exe,.cache*), chmod 0755 on Unix, and executed detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}) or cmd.exe. No hash or signature verification is performed, destinations are not publisher-controlled, and hostnames and the require("child_"+"process") call are string-split to evade static scanners. The Logger export is a cover story shadowing an install/import-time remote-code-execution dropper.

Malicious versions

1 flagged
35.3.6

Indicators of compromise (SHA-256)

d77aab31095b1d13ea26c5ca29398e01a205ed0766fe95d5d8978751ebd75e35

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-desktop-bnpl-header-catalog (version 35.3.6).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015453

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-desktop-bnpl-header-catalog-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-desktop-bnpl-header-catalog (npm) malicious package — MAL-2026-12926 | O3 Security