bnpl-blocks-mobile-bnpl-partnersnpm
bnpl-blocks-mobile-bnpl-partners is a confirmed malicious npm package (MAL-2026-13000) that executes malicious code on install (malicious version 35.8.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-partners (npm)
What this malware does
index.js unconditionally requires helpers.js, which on module load fetches a platform-specific binary from string-split-obfuscated Cloudflare Workers subdomains (oob-worker.cf*.workers.dev) with a DNS/TXT fallback under *.dl.wel1.ru, writes the payload to /var/tmp or %TEMP% under cover-story filenames (.cache<hex> on Linux, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start. Hostnames are assembled at runtime from split arrays joined with.join('') to hide the destinations from static scanners, and cp/fs API names are reconstructed via string concatenation (require('child_'+'process'), fs['chmod'+'Sync']). A parallel dropper implementation is bundled in lib/telemetry.js under an 'analytics SDK' cover story with the same fetch, base64-decode, chmod 755, and detached-shell-spawn primitives. Requiring this package on any platform executes attacker-controlled code on the installer's host.
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-partners (version 35.8.8). 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-partners across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-bnpl-partners 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-partners 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-partners 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-partners-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.