bnpl-blocks-analyticsnpm
bnpl-blocks-analytics is a confirmed malicious npm package (MAL-2026-12861) that typosquats a legitimate package to trick installs (malicious version 35.3.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-analytics (npm)
What this malware does
On require('bnpl-blocks-analytics'), index.js loads compat.js whose top-level start() function downloads an OS-specific binary from Cloudflare Workers hosts assembled at runtime by joining split string arrays (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT base64 fallback resolving to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to /var/tmp or %TEMP% under masquerading names (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmodded to 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', filePath+' &']) or cmd equivalent. No signature or hash verification is performed. A parallel dropper implementation is bundled in lib/telemetry.js, framed as an 'analytics SDK', using base64-chunk decoding and the same chmod+spawn pattern. Destination hostnames are obfuscated via string-array.join() and the payload filenames impersonate.NET diagnostic tooling.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-analytics (version 35.3.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-analytics across your stack and pipelines.
If you installed it — respond
bnpl-blocks-analytics is a typosquat — you almost certainly intended a legitimately-named package. Remove bnpl-blocks-analytics, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bnpl-blocks-analytics 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-analytics 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-analytics-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.