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

bnpl-blocks-desktop-bnpl-separatornpm

Advisory published Updated

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

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

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

What this malware does

On require of the package's main entry, _shim.js unconditionally fetches a platform-specific binary over HTTPS from hardcoded hostnames assembled via array.join() to defeat literal string search (e.g. oob-worker.cf10{0,1,2}-*.workers.dev), with a DNS TXT-record fallback channel that reassembles a base64-encoded payload from chunked TXT queries against *.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under a disguised name, chmod'd to 0755 on POSIX, and spawned detached via /bin/sh -c or cmd.exe /c start. No signature or hash verification is performed and the destination hosts are not first-party to the package's stated purpose. A second, structurally identical dropper module ships at lib/telemetry.js containing the same HTTPS-fetch + base64-decode + chmod 755 + /bin/sh spawn pattern, though not currently wired into main in this version. Package name and 'analytics/telemetry' framing serve as cover; destination-string obfuscation and the DNS-TXT payload channel are consistent with evasion of static indicator scanning.

Malicious versions

1 flagged
35.5.8

Indicators of compromise (SHA-256)

a925d2ffafa8ffd0f27b1072b73d895eda640c78f1444312dcf9e09c92072216

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-desktop-bnpl-separator (version 35.5.8).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015443

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

bnpl-blocks-desktop-bnpl-separator (npm) malicious package — MAL-2026-12939 | O3 Security