bnpl-blocks-atom-bnpl-promocodenpm
bnpl-blocks-atom-bnpl-promocode is a confirmed malicious npm package (MAL-2026-12887) that steals credentials and exfiltrates sensitive data (malicious version 35.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-promocode (npm)
What this malware does
On require of the package's main entry, helpers.js runs a bootstrap() routine that downloads an OS-specific binary from Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, cf99-9b3.workers.dev, cf100-416.workers.dev) with a DNS TXT fallback under *.dl.wel1.ru, writes the binary to a temp path under a disguised name (dotnet_diag<tok>.exe on Windows,.cache_<tok> on POSIX), chmods it 0755, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true, stdio:"ignore"}).unref() (or spawn("cmd"...) on Windows). Endpoint hostnames are assembled by Array.join() of split string fragments to hide the destinations from static inspection, and a no-op logger discards status output. A stamp file (/tmp/.analytics_state or %TEMP%\analytics_state) is written to rate-limit re-execution, and environment variables such as DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, and DO_NOT_TRACK are checked as a telemetry cover story. No signature or hash verification is performed on the downloaded payload.
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-promocode (version 35.9.1). 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-promocode across your stack and pipelines.
If you installed it — respond
bnpl-blocks-atom-bnpl-promocode 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-promocode 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-promocode 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-promocode-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.