bnpl-blocks-independent-bnpl-searchnpm
bnpl-blocks-independent-bnpl-search is a confirmed malicious npm package (MAL-2026-12341) that executes malicious code on install (malicious version 20.2.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-independent-bnpl-search (npm)
What this malware does
On require of the package, index.js loads _runtime.js which downloads a platform-specific binary from runtime-assembled *.workers.dev hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), writes it under /tmp or %TEMP% with a disguised name, chmods 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd /c start. Destination hostnames are assembled from split string fragments joined at runtime to evade static URL scanners. When HTTPS fetches fail, the loader falls back to base64-encoded chunks retrieved from DNS TXT records under attacker-controlled subdomains of dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), reassembling and executing the payload from the encoded chunks. A second file lib/telemetry.js shipped in the tarball contains a matching download-decode-chmod-spawn class with the same operator shape.
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-search (version 20.2.9). 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-search across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-search 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-search 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-search 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-search-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.