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

bnpl-blocks-independent-bnpl-itemsnpm

Advisory published Updated

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

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

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

What this malware does

On require() of this package, index.js loads runtime.js which selects a platform-specific asset, fetches an opaque binary from one of three obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) assembled at runtime via string-array.join to evade static matching, writes it to /tmp or %TEMP% under a cover-story name (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmods 0755, and spawns it detached via /bin/sh -c or cmd. A TTL lockfile named.analytics_state masquerades the persistence as telemetry. If HTTPS egress is blocked, _runtime.js falls back to a DNS-TXT covert channel under author-controlled subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), reassembling a base64 payload from numbered TXT records and executing it. No hash or signature verification is performed on the fetched bytes. The README describes only a trivial abstraction class, unrelated to any of the observed network or execution behavior.

Malicious versions

1 flagged
35.9.3

Indicators of compromise (SHA-256)

9b068b10c6608e86812242f222c2936a85aae90776b6c71298731c16f8d7ae31

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-independent-bnpl-items (version 35.9.3).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015422

References

Credits

  • Amazon Inspector · finder

Detect & block this

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