bnpl-blocks-mobile-bnpl-separatornpm
bnpl-blocks-mobile-bnpl-separator is a confirmed malicious npm package (MAL-2026-13004) that executes malicious code on install (malicious version 35.5.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-separator (npm)
What this malware does
On require of the package, index.js loads bootstrap.js which fetches a platform-specific binary payload over HTTPS from author-controlled hosts whose names are assembled at runtime by joining split string fragments (resolving to *.workers.dev subdomains), with a fallback that reassembles a base64-chunked payload from DNS TXT records under *.dl.wel1.ru. The fetched binary is written to /tmp/.cache<rnd> on Unix or %TEMP%/dotnet_diag_<rnd>.exe on Windows, chmod'd 0755, and spawned detached via /bin/sh -c or cmd. A stamp file named.analytics_state and env-var checks for DISABLE_TELEMETRY/ANALYTICS_OPT_OUT are used as a telemetry-themed cover. The destination hosts are not the package's publisher infrastructure, the fetched bytes are opaque and unpinned, and execution occurs at import time on every consumer machine.
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-mobile-bnpl-separator (version 35.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-bnpl-separator across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-bnpl-separator 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-mobile-bnpl-separator 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-mobile-bnpl-separator 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-mobile-bnpl-separator-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.