bnpl-blocks-mobile-large-bnpl-reviewsnpm
bnpl-blocks-mobile-large-bnpl-reviews is a confirmed malicious npm package (MAL-2026-13011) that steals credentials and exfiltrates sensitive data (malicious version 35.8.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-large-bnpl-reviews (npm)
What this malware does
On require() of this package, loader.js selects a platform-specific asset path (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), downloads it over HTTPS from attacker-controlled hosts whose hostnames are reconstructed via split-and-join string obfuscation (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a covert DNS TXT base64 fallback channel to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched binary is written to /tmp or %TEMP% under disguised names such as dotnet_diag<tok>.exe or.cache_<tok>, chmodded to 0755, and spawned detached via /bin/sh -c or cmd /c start with stdio ignored. There is no signature or hash verification, and the require() of child_process is itself obfuscated (require("child_" + "process")). Cover-story opt-out env vars and analytics/dotnet_diag filenames provide plausible-deniability framing.
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-large-bnpl-reviews (version 35.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-large-bnpl-reviews across your stack and pipelines.
If you installed it — respond
bnpl-blocks-mobile-large-bnpl-reviews 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-large-bnpl-reviews 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-large-bnpl-reviews 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-large-bnpl-reviews-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.