bnpl-blocks-atom-bnpl-breadcrumbsnpm
bnpl-blocks-atom-bnpl-breadcrumbs is a confirmed malicious npm package (MAL-2026-12866) 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-atom-bnpl-breadcrumbs (npm)
What this malware does
On require() of the package, index.js loads polyfill.js, which fetches a platform-specific opaque binary from obfuscated Cloudflare Workers subdomains (oob-worker.cf100-.workers.dev, oob-worker.cf101-.workers.dev, etc.) and, if HTTPS delivery fails, falls back to reassembling the payload from base64-encoded DNS TXT records under *.dl.wel1.ru (query c.<domain> for a chunk count, then concatenate N.<domain> TXT records). The retrieved bytes are written to /var/tmp or %TEMP% under a disguised filename (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 0755'd, and detach-spawned via /bin/sh -c "<file> &" or cmd /c start, with.unref() so the process outlives the require() call. C2 hostnames are assembled at runtime by array-join splits (["oob-","worker.cf10","0-416.w","orkers.d","ev"].join(""), ['sdk.dl.wel1','.ru'].join("")) to defeat static string scanning, and the code respects DO_NOT_TRACK/DISABLE_TELEMETRY environment variables as a review-evasion gate. The staged filenames impersonate legitimate diagnostic tooling and a hidden marker file (.analytics_state) is used to track prior execution. No verification (hash, signature, pinning) is performed on the fetched binary.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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-atom-bnpl-breadcrumbs (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-atom-bnpl-breadcrumbs across your stack and pipelines.
If you installed it — respond
bnpl-blocks-atom-bnpl-breadcrumbs 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-atom-bnpl-breadcrumbs 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-atom-bnpl-breadcrumbs 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-atom-bnpl-breadcrumbs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.