bnpl-blocks-independent-bnpl-documentsnpm
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-independent-bnpl-documents (version 35.6.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-independent-bnpl-documents across your stack and pipelines.
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.
Did it already run?
If bnpl-blocks-independent-bnpl-documents was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bnpl-blocks-independent-bnpl-documents before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
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.