bnpl-blocks-independent-bnpl-faqnpm
bnpl-blocks-independent-bnpl-faq is a confirmed malicious npm package (MAL-2026-12955) that executes malicious code on install (malicious version 35.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-independent-bnpl-faq (npm)
What this malware does
On require() of this package, index.js loads runtime.js which downloads a platform-specific binary over HTTPS from obfuscated hosts (oob-worker.cf<n>-<n>.workers.dev, assembled by joining fragmented string arrays to evade static scans), writes it to a disguised path in /tmp or %TEMP% (e.g..cache<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. If HTTPS fails, _runtime.js falls back to reassembling a base64-encoded binary from DNS TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru subdomains and executes it via the same path. No hash or signature verification is performed, and destination hostnames are hidden via array-join obfuscation. The package advertises itself as a BNPL FAQ adapter; the declared purpose does not require binary downloads or a DNS covert channel.
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-faq (version 35.1.1). 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-faq across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-faq 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-faq 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-faq 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-faq-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.