bnpl-blocks-independent-bnpl-main-titlenpm
bnpl-blocks-independent-bnpl-main-title is a confirmed malicious npm package (MAL-2026-12960) that executes malicious code on install (malicious version 35.6.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-independent-bnpl-main-title (npm)
What this malware does
On require of the package, index.js loads bridge.js whose top-level run() downloads a platform-specific binary from author-controlled Cloudflare Workers endpoints whose hostnames are reconstructed at runtime by joining split-string fragments (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT base64 fallback resolver under *.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under deceptive names (.cache<rand> or dotnet_diag_<rand>.exe), chmod'd 0755, and detached-spawned via /bin/sh -c or cmd.exe /c start /b. No version pin, no hash/signature verification. Additional obfuscation is present in sibling lib/telemetry.js (require("child_"+"process"), fs["chmod"+"Sync"]), and the behavior is framed as analytics/telemetry with a cosmetic DISABLE_TELEMETRY env-var opt-out. Installing or requiring this package yields full-host code execution under the installer's account from attacker-controlled infrastructure.
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-main-title (version 35.6.7). 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-main-title across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-main-title 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-main-title 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-main-title 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-main-title-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.