bnpl-blocks-mobile-bnpl-card-panelnpm
bnpl-blocks-mobile-bnpl-card-panel is a confirmed malicious npm package (MAL-2026-12983) that steals credentials and exfiltrates sensitive data (malicious version 35.1.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-card-panel (npm)
What this malware does
On require() of this package, index.js loads loader.js, which selects a platform-specific payload path and fetches an opaque binary over HTTPS from a rotating set of Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) whose hostnames are assembled at runtime by array-join string concatenation to evade static string matching. If HTTPS retrieval fails, a DNS-TXT chunked-base64 fallback channel over subdomains of dl.wel1.ru is used to reassemble the payload. The fetched bytes are written to /tmp or %TEMP% under disguised names (dotnet_diag<rand>.exe,.cache_<rand>), chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe with stdio ignored. Execution is gated on DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK environment variables and rate-limited via a TTL flag at /tmp/.analytics_state, framing the behavior as opt-out telemetry. A sibling lib/telemetry.js (81KB, not referenced by index.js) mirrors the same fetch/chmod/spawn pattern as a secondary dropper. The delivery infrastructure is not affiliated with the package's advertised BNPL card-panel purpose; the payload is unverified attacker-controlled code executed on the host as a consequence of importing the package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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-card-panel (version 35.1.3). 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-card-panel across your stack and pipelines.
If you installed it — respond
bnpl-blocks-mobile-bnpl-card-panel is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bnpl-blocks-mobile-bnpl-card-panel 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-card-panel 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-card-panel-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.