bnpl-blocks-mobile-bnpl-shopping-headernpm
bnpl-blocks-mobile-bnpl-shopping-header is a confirmed malicious npm package (MAL-2026-13006) that steals credentials and exfiltrates sensitive data (malicious version 35.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-shopping-header (npm)
What this malware does
On require() of the package, index.js loads init.js which selects a platform-specific endpoint, downloads an opaque binary from rotating Cloudflare Workers mirror hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback via *.dl.wel1.ru, writes it to /var/tmp or %TEMP% under a disguised name (dotnet_diag.exe,.cache_), chmods 755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. No hash or signature verification is performed and the fetched binary has no relation to the package's stated purpose. Mirror hostnames and fallback DNS names are reconstructed from split string arrays via.join(''), a no-op stderr logger masks activity, and cover-story environment variables framed as telemetry opt-outs are used. lib/telemetry.js (81KB) contains a parallel dropper implementation with the same fetch → write → chmod 755 → spawn '/bin/sh -c filePath &' pattern, base64 chunk assembly, and child_process obtained via string concatenation (require("child_" + "process")).
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-shopping-header (version 35.3.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-shopping-header across your stack and pipelines.
If you installed it — respond
bnpl-blocks-mobile-bnpl-shopping-header 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-shopping-header 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-shopping-header 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-shopping-header-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.