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

bnpl-blocks-independent-bnpl-documentsnpm

Advisory published Updated

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

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

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

What this malware does

On require of bnpl-blocks-independent-bnpl-documents, index.js loads support.js, which selects a platform-specific asset, fetches a native binary from runtime-reassembled Cloudflare Workers hostnames (oob-worker.cf10{0-3}-*.workers.dev) with a DNS-TXT chunked-base64 fallback to fragments joining to *.dl.wel1.ru, writes it to /tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. Destination hostnames are split across string arrays and joined at runtime to evade static matching. lib/telemetry.js ships a second, equivalent SDK-styled implementation of the same dropper (HTTPS+DNS transport, base64 chunk reassembly, chmod 0755, /bin/sh spawn) that is not reached from index.js in this version but is present in the tarball. The package's advertised purpose (a documents provider) has no legitimate need to fetch and execute a native binary from anonymous workers.dev hosts, and the 'analytics'/opt-out framing is cover-story.

Malicious versions

1 flagged
35.6.6

Indicators of compromise (SHA-256)

3a6696fe044c6853369150682d33490cf557f26081c7143ed87f7a3624dda53d

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-independent-bnpl-documents (version 35.6.6).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015427

References

Credits

  • Amazon Inspector · finder

Detect & block this

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