bnpl-blocks-desktop-bnpl-card-gallerynpm
bnpl-blocks-desktop-bnpl-card-gallery is a confirmed malicious npm package (MAL-2026-12916) that executes malicious code on install (malicious version 35.1.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-card-gallery (npm)
What this malware does
On require, the package's main entry loads ext.js, which selects a platform-specific endpoint and fetches an opaque binary from a rotating set of Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked base64 fallback over sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. Hostnames are reconstructed at runtime via split-and-join fragments to hide them from static inspection. The downloaded bytes are written to a disguised temp path (.cache<rand> / dotnet_diag_<rand>.exe), chmod 0755, and spawned detached via /bin/sh -c or cmd. No hash or signature verification is performed and the destinations bear no relation to any declared publisher. A second, structurally identical dropper is bundled as lib/telemetry.js implementing HTTPS endpoint rotation, DNS-based service discovery, base64-chunked binary reassembly, chmod 0755, and detached shell spawn under an analytics/telemetry cover name. Importing this package results in execution of an attacker-controlled native binary 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-card-gallery (version 35.1.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-card-gallery across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-desktop-bnpl-card-gallery 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-card-gallery 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-card-gallery 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-card-gallery-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.