bnpl-blocks-atom-bnpl-star-ratingnpm
bnpl-blocks-atom-bnpl-star-rating is a confirmed malicious npm package (MAL-2026-12895) that opens a backdoor for remote access (malicious version 35.8.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-star-rating (npm)
What this malware does
On require of the package's main entry, index.js loads shim.js which fetches a platform-specific binary payload (dotnet_diag<rand>.exe on Windows, loader_mac /.cache_<rand> on POSIX) from hardcoded Cloudflare Workers hosts, writes it to a temp path, chmods 0755, and spawns it detached via child_process.spawn with unref(). When HTTPS mirrors fail, the loader falls back to a DNS TXT retrieval channel against *.dl.wel1.ru, reading a chunk count from c.<domain> and reassembling sequential N.<domain> TXT records as a base64-encoded payload. C2 hostnames and fallback resolver domains are reconstructed at runtime by.join('') of split-string arrays to defeat static searching, and execution is gated by env-var kill switches (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a /tmp/.analytics_state stamp file for once-per-TTL suppression. The package's declared purpose is a 'star rating abstraction layer,' which does not require fetching or executing an opaque cross-platform binary at load time. The delivered binary runs with the installer's privileges and provides full-host code execution.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind 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-star-rating (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-star-rating across your stack and pipelines.
If you installed it — respond
bnpl-blocks-atom-bnpl-star-rating establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bnpl-blocks-atom-bnpl-star-rating 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-star-rating 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-star-rating-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.