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

bnpl-blocks-independent-bnpl-tablenpm

Advisory published Updated

bnpl-blocks-independent-bnpl-table is a confirmed malicious npm package (MAL-2026-12971) that executes malicious code on install (malicious version 35.3.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-independent-bnpl-table (npm)

MAL-2026-12971
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-independent-bnpl-table

What this malware does

Requiring bnpl-blocks-independent-bnpl-table transitively loads compat.js, which auto-invokes a start() routine at module load. The routine downloads a platform-specific native executable over HTTPS from Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS TXT fallback under *.dl.wel1.ru for base64-encoded payload delivery. Hostnames are reconstructed at runtime by joining split string fragments to hide them from casual inspection. The downloaded binary is written to /tmp (Unix) as a hidden file named.cache<hex> or to %TEMP% (Windows) under a masquerading name like dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. A stamp file named.analytics_state and 'telemetry'/'graceful degradation' labels form a cover story. The delivered binary is opaque, unpinned, unverified, and the fetch destinations do not match the package publisher and are unrelated to the package's stated BNPL-table purpose.

Malicious versions

1 flagged
35.3.7

Indicators of compromise (SHA-256)

0c9351985ce827df7a44d4de41728052bf0a0013df223954d273b2ad8d6735bf

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-independent-bnpl-table (version 35.3.7).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015413

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-independent-bnpl-table-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-independent-bnpl-table (npm) malicious package — MAL-2026-12971 | O3 Security