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

bnpl-blocks-independent-bnpl-main-titlenpm

Advisory published Updated

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

Malicious code in bnpl-blocks-independent-bnpl-main-title (npm)

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

What this malware does

On require of the package, index.js loads bridge.js whose top-level run() downloads a platform-specific binary from author-controlled Cloudflare Workers endpoints whose hostnames are reconstructed at runtime by joining split-string fragments (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT base64 fallback resolver under *.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under deceptive names (.cache<rand> or dotnet_diag_<rand>.exe), chmod'd 0755, and detached-spawned via /bin/sh -c or cmd.exe /c start /b. No version pin, no hash/signature verification. Additional obfuscation is present in sibling lib/telemetry.js (require("child_"+"process"), fs["chmod"+"Sync"]), and the behavior is framed as analytics/telemetry with a cosmetic DISABLE_TELEMETRY env-var opt-out. Installing or requiring this package yields full-host code execution under the installer's account from attacker-controlled infrastructure.

Malicious versions

1 flagged
35.6.7

Indicators of compromise (SHA-256)

85d01515b559e3e623341b5838615add9439fc1d3942948acb3ca2aee86e9579

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-independent-bnpl-main-title (version 35.6.7).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015423

References

Credits

  • Amazon Inspector · finder

Detect & block this

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