bnpl-blocks-atom-bnpl-faq-itemnpm
bnpl-blocks-atom-bnpl-faq-item is a confirmed malicious npm package (MAL-2026-13528) that executes malicious code on install (malicious version 35.8.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-faq-item (npm)
What this malware does
The package's main entry (index.js) requires./ext at module load. ext.js downloads a platform-specific binary from hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) — assembled via string-split/join to defeat static scanners — with a DNS-TXT chunked-download fallback under *.dl.wel1.ru (c.<domain> for chunk count, <i>.<domain> for base64 payload chunks). The fetched bytes are written to /var/tmp/.cache<rnd> on POSIX or %TEMP%\dotnet_diag<rnd>.exe on Windows, chmod 0755, and spawned detached via /bin/sh -c or cmd. A stamp file named.analytics_state and the dotnet_diag_* filename disguise are used to blend into normal system activity. Any require()/import of the package triggers download-and-execute of opaque attacker-controlled code on the installer's machine.
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-atom-bnpl-faq-item (version 35.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-bnpl-faq-item across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-faq-item 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-atom-bnpl-faq-item 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-atom-bnpl-faq-item 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-atom-bnpl-faq-item-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.