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

bnpl-blocks-independent-bnpl-separatornpm

Advisory published Updated

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

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

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

What this malware does

Requiring this package triggers init.js, which selects a platform-specific payload URL from string-concat-obfuscated Cloudflare Workers hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT base64 reassembly fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /tmp or the Windows temp directory under disguised names such as dotnet_diag.exe and.cache_, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Cover-story naming (.analytics_state run-once marker, DISABLE_TELEMETRY/DO_NOT_TRACK env checks) frames the behavior as analytics. A secondary dropper with the same fetch/writeFile/chmod/spawn shape ships in lib/telemetry.js, using base64-decoded payload chunks and split-string require('child_'+'process'). The destinations are non-publisher infrastructure, the payload bytes are opaque, and hostnames plus module names are assembled at runtime to evade static review.

Malicious versions

1 flagged
35.3.8

Indicators of compromise (SHA-256)

a8e34f125883bf487e46fede3b2094978e853711c0688c8712cc5628e929f0ad

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-independent-bnpl-separator (version 35.3.8).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015404

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-independent-bnpl-separator-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
bnpl-blocks-independent-bnpl-separator (npm) malicious package — MAL-2026-12969 | O3 Security