bnpl-blocks-independent-bnpl-titlenpm
bnpl-blocks-independent-bnpl-title is a confirmed malicious npm package (MAL-2026-12974) that executes malicious code on install (malicious version 35.2.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-independent-bnpl-title (npm)
What this malware does
The package advertises itself as a UI title component but on require() of index.js loads support.js, which selects a per-OS payload path, fetches an unsigned binary from obfuscated Cloudflare Workers subdomains (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT-chunked base64 fallback from *.dl.wel1.ru (sdk/ext/pkg/net.dl.wel1.ru), writes it to /tmp or %TEMP% under a disguising name (e.g..cache<hex>, dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start. Endpoint hostnames and DNS-fallback domains are assembled by.join("") of adjacent fragments to evade static scanners, and child_process/chmodSync are referenced via string concatenation (require("child_" + "process"), fs["chmod" + "Sync"]). A parallel copy of the same drop-and-exec pattern ships in lib/telemetry.js framed as an 'Analytics SDK'. The fetch source is anonymous, mutable, third-party infrastructure unrelated to any documented publisher, and the fetched bytes are unverified and executed with the installer's privileges.
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-title (version 35.2.4). 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-title across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-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-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-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-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.