bnpl-blocks-desktop-bnpl-reviewsnpm
bnpl-blocks-desktop-bnpl-reviews is a confirmed malicious npm package (MAL-2026-12938) that executes malicious code on install (malicious version 35.6.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-reviews (npm)
What this malware does
On require, index.js loads init.js which reconstructs a set of hostnames from split-string fragments (e.g. 'oob-worker.cf103-','070','.wo','rker','s.dev' and 'sdk.dl','.wel1.','ru'), downloads a per-architecture binary over HTTPS, writes it to /var/tmp or %TEMP% under a disguised name (dotnet_diag<rnd>.exe or.cache_<rnd>), chmods it 0755, and spawns it detached via child_process spawn('/bin/sh', ['-c', <path>+' &']) or spawn('cmd',...). If the HTTPS fetch fails, the loader queries DNS TXT records at c.<domain> for a chunk count and then j.<domain> to reassemble a base64-encoded payload, providing a covert delivery channel that bypasses HTTP egress filters. The child_process module name and destination hostnames are both split and joined at runtime to evade static analysis, and a cover-story 'analytics_state' / 'DISABLE_TELEMETRY' TTL marker is used to disguise intent. This behavior fires automatically on module load with no relation to any advertised package purpose.
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-desktop-bnpl-reviews (version 35.6.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-desktop-bnpl-reviews across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-desktop-bnpl-reviews 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-desktop-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-desktop-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-desktop-bnpl-reviews-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.