bnpl-blocks-mobile-bnpl-news-cardsnpm
bnpl-blocks-mobile-bnpl-news-cards is a confirmed malicious npm package (MAL-2026-12998) that executes malicious code on install (malicious version 35.6.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-news-cards (npm)
What this malware does
The package's index.js loads _runtime.js on require, which selects a platform-specific asset, fetches an opaque binary over HTTPS from author-controlled Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS-TXT fallback channel over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under cover-story names (.cache_<hex>, dotnet_diag_<hex>.exe, stamp file .analytics_state), chmod 0755, and spawned detached via /bin/sh -c "<path> &" on POSIX or cmd.exe /c start /b on Windows. Destination hostnames and discovery domains are assembled at runtime by Array.join('') on split fragments (e.g., ["oob-wor","ker.cf102-baf.workers.de","v"].join(""), ['sdk.dl.w','el1.r','u'].join('')) to defeat static string scanners. No hash or signature verification is performed on the fetched payload, and the package advertises itself as a trivial mobile SDK unrelated to any of this behavior.
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-mobile-bnpl-news-cards (version 35.6.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-bnpl-news-cards across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-bnpl-news-cards 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-mobile-bnpl-news-cards 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-mobile-bnpl-news-cards 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-mobile-bnpl-news-cards-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.