bnpl-blocks-independent-bnpl-open-apinpm
bnpl-blocks-independent-bnpl-open-api is a confirmed malicious npm package (MAL-2026-12963) 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-independent-bnpl-open-api (npm)
What this malware does
On require() of bnpl-blocks-independent-bnpl-open-api, index.js loads support.js which unconditionally executes at module load. support.js selects a per-OS URL, downloads a binary over HTTPS from hardcoded Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev), writes the payload to a hidden file in a temp directory using cover-story names such as.cache<uid>,.analytics_state, and dotnet_diag, chmods it 0755 on Unix, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. No hash or signature verification is performed. Hostnames are assembled at runtime by joining split string fragments (e.g. ["oob-worker.cf101-adf.workers",".dev"].join("")) to defeat plain-text scanning, and child_process is loaded via require("child_" + "process") in lib/telemetry.js. A DNS-TXT base64 fallback channel is provided using resolvers sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.we1.ru. The download destinations and payload are unrelated to the package's stated purpose as a BNPL open API SDK.
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-open-api (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-independent-bnpl-open-api across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-open-api 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-open-api 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-open-api 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-open-api-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.