bnpl-blocks-desktop-bnpl-faqnpm
bnpl-blocks-desktop-bnpl-faq is a confirmed malicious npm package (MAL-2026-12920) that executes malicious code on install (malicious version 35.6.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-faq (npm)
What this malware does
On require() of the package, index.js loads support.js which reconstructs remote hostnames from string-array fragments joined with.join('') to defeat literal-string scanning. It then fetches platform-specific binaries via https.get from oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, and oob-worker.cf100-416.workers.dev, writes them to /var/tmp or %TEMP% under disguised names (.cache<rand>, dotnet_diag_<rand>.exe), chmods 0755, and detach-executes them via spawn('/bin/sh') or spawn('cmd'). A DNS-TXT covert channel to sdk.dl.wel1.ru provides an out-of-band fallback for chunked base64 data. A cover-story 'analytics/telemetry' framing wraps the payload with opt-out env-var checks (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a hidden run-once marker at /tmp/.analytics_state to reduce repeated observation. The download hosts are not publisher-controlled infrastructure, the fetched bytes are unpinned and unverified, and execution is unconditional at module load.
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-desktop-bnpl-faq (version 35.6.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-desktop-bnpl-faq across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-desktop-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-desktop-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-desktop-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-desktop-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.