MAL-2026-12925 Malicious code in bnpl-blocks-desktop-bnpl-header (npm)
Malicious package
Published
MAL-2026-12925 is a malicious package: bnpl-blocks-desktop-bnpl-header (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-12925/ (Markdown: https://insights.sbomify.com/MAL-2026-12925/index.md)
- Package
- bnpl-blocks-desktop-bnpl-header
- Registry
- npm
What is MAL-2026-12925?
MAL-2026-12925 is a malicious package in bnpl-blocks-desktop-bnpl-header, published on 5 Aug 2026.
Official description
On require() of this package, index.js loads bridge.js, which reconstructs C2 hostnames from split string fragments (e.g. ["oob-worker",".cf","10","3-070.worke","rs.d","ev"].join("")) to resolve oob-worker.cf*.workers.dev endpoints and a DNS-TXT fallback under *.dl.wel1.ru. It downloads a platform-specific binary (/pkg/package, /pkg/package-arm64, /pkg/loader_mac, /pkg/package.exe), writes it to /var/tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh or cmd.exe /c start /b, using a marker file to suppress repeat execution. A DNS-TXT channel reassembles base64 chunks from sequentially numbered TXT records as a fallback. Cover strings referencing analytics/telemetry/dotnet_diag are misdirection; the destinations are non-publisher, anonymous Cloudflare Workers and Russian DNS hosts, and the fetched bytes are opaque binaries executed on the installer's host. An additional 81 KB lib/telemetry.js is shipped but not reached from index.js or _bridge.js.
What should I do about MAL-2026-12925?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.