bnpl-blocks-atom-bnpl-reviews-counternpm
bnpl-blocks-atom-bnpl-reviews-counter is a confirmed malicious npm package (MAL-2026-12891) that executes malicious code on install (malicious version 35.3.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-atom-bnpl-reviews-counter (npm)
What this malware does
On require of this package, index.js loads platform.js which runs at import time. It reconstructs a list of destination hosts by string-splitting fragments (assembling oob-worker.cf*.workers.dev endpoints and *.dl.wel1.ru fallbacks), selects an architecture-specific asset, fetches a native binary over HTTPS, writes it to /var/tmp or %TEMP% under a disguised name (.cache<rand> on POSIX, dotnet_diag_<rand>.exe on Windows), chmods it 0755, and spawns it detached via /bin/sh -c "<path> &" or cmd /c start /b. If the HTTPS fetch fails, a covert DNS-TXT channel is used: a chunk count is read from c.<domain> TXT records and base64 payload fragments are reassembled from N.<domain> TXT records. An anti-repeat flag file at /tmp/.analytics_state suppresses repeat execution. No hash or signature verification is performed on the fetched binary, the destination hosts are not the package's publisher, the hostnames are obfuscated via string-splitting to defeat static inspection, and the package's advertised purpose (a BNPL reviews counter) has no legitimate need to fetch and execute a native binary at import time.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind 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-reviews-counter (version 35.3.6). 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-reviews-counter across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-atom-bnpl-reviews-counter from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bnpl-blocks-atom-bnpl-reviews-counter 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-reviews-counter 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-reviews-counter-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.