bnpl-blocks-mobile-bnpl-documentsnpm
bnpl-blocks-mobile-bnpl-documents is a confirmed malicious npm package (MAL-2026-12986) that executes malicious code on install (malicious version 35.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-documents (npm)
What this malware does
The package's main entry require()s./compat on load. compat.js runs an async init() at module load that fetches an opaque binary from hardcoded Cloudflare Workers subdomains (oob-worker.cf*.workers.dev), with a DNS-TXT fallback under sdk.dl.wel1.ru that base64-reassembles bytes. Destination hostnames are string-joined at runtime from substring arrays to defeat static URL scanning. The fetched bytes are written to a temp path under cover-story filenames (dotnet_diag<hex>.exe on Windows,.cache<hex> on Unix), chmod 0755'd, and launched detached and unref'd via cmd.exe /c start /b or /bin/sh -c '<path> &'. A second dropper implementation in lib/telemetry.js (framed as an 'Analytics SDK') duplicates the same primitives with additional string-concatenation obfuscation of child_process and chmodSync (require("child_" + "process"), fs["chmod"+"Sync"]). Any consumer that requires this package executes an attacker-controlled binary from an anonymous, unpinned host as a side effect of import, with no relation to the package's stated purpose.
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-mobile-bnpl-documents (version 35.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-bnpl-documents across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-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-mobile-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-mobile-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-mobile-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.