bnpl-blocks-desktop-bnpl-grid-containernpm
bnpl-blocks-desktop-bnpl-grid-container is a confirmed malicious npm package (MAL-2026-12924) that executes malicious code on install (malicious version 35.2.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-grid-container (npm)
What this malware does
index.js unconditionally requires./setup.js, which on module load selects an OS/arch-specific asset path and downloads a binary from Cloudflare Workers hostnames assembled via split-string obfuscation (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-TXT base64-chunk fallback channel over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The downloaded bytes are written to a disguised temp filename (.cache_<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c fp & or cmd.exe /c start /b. Destination hostnames are constructed at runtime by joining fragmented string arrays, and a TTL flag file throttles re-execution. Installing or requiring this package causes attacker-controlled code to run on the installer's host.
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-grid-container (version 35.2.9). 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-grid-container across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-desktop-bnpl-grid-container 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-grid-container 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-grid-container 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-grid-container-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.