bnpl-blocks-desktop-bnpl-navigationnpm
bnpl-blocks-desktop-bnpl-navigation is a confirmed malicious npm package (MAL-2026-12932) that executes malicious code on install (malicious version 35.3.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-desktop-bnpl-navigation (npm)
What this malware does
On require of the package, index.js loads runtime.js which selects a platform-specific endpoint, downloads an opaque binary over HTTPS from obfuscated Cloudflare Worker hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), writes it to a hidden temp path (e.g.,.cache, dotnet_diag_.exe under /tmp), chmods 0755, and spawns it detached via /bin/sh or cmd. Destination hostnames are constructed by array-join (e.g., ["oob-worker.cf100-416.workers.d","ev"].join("")) to defeat static string scanning. If HTTPS fetch fails, the loader falls back to a DNS-TXT covert channel: it queries c.<domain> under *.dl.wel1.ru (sdk/ext/pkg/net) for a chunk count and reassembles base64 payload from numbered TXT records, executing the reassembled bytes identically. A mirrored copy of the dropper exists in lib/telemetry.js and additionally hides child_process via require("child_"+"process"). The fetched binary is unpinned and unverified; content is attacker-controlled and executed with the installer's privileges.
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-navigation (version 35.3.2). 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-navigation across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-desktop-bnpl-navigation 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-navigation 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-navigation 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-navigation-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.