bnpl-blocks-independent-bnpl-mobile-applicationnpm
bnpl-blocks-independent-bnpl-mobile-application is a confirmed malicious npm package (MAL-2026-12961) that executes malicious code on install (malicious version 35.7.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-independent-bnpl-mobile-application (npm)
What this malware does
On require() of this package, index.js loads adapter.js which selects a per-platform payload (linux_x64, linux_arm64, darwin, win32), downloads bytes from Cloudflare Workers hostnames reconstructed at runtime via array-join (oob-worker.cf102-baf.workers.dev, cf99-9b3.workers.dev, cf100-416.workers.dev) with a DNS-TXT covert-channel fallback (c.<domain> chunk count then N.<domain> base64 TXT chunks against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), writes the payload to disguised paths (/tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe), chmods 0755, and spawns it detached via cp.spawn("/bin/sh",["-c", fp+" &"],{detached:true}) or cmd /c start /b. Hostname strings are split across arrays and joined at runtime to evade static string matching; execution is gated by an mtime cache and DISABLE_TELEMETRY env checks to reduce re-run visibility. The fetched binary is publisher-mismatched, unpinned, unsigned, and hosted on anonymous infrastructure unrelated to any documented 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-independent-bnpl-mobile-application (version 35.7.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-independent-bnpl-mobile-application across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-independent-bnpl-mobile-application 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-independent-bnpl-mobile-application 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-independent-bnpl-mobile-application 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-independent-bnpl-mobile-application-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.