MAL-2026-12927 Malicious code in bnpl-blocks-desktop-bnpl-header-search (npm)
Malicious package
Published
MAL-2026-12927 is a malicious package: bnpl-blocks-desktop-bnpl-header-search (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-12927/ (Markdown: https://insights.sbomify.com/MAL-2026-12927/index.md)
- Package
- bnpl-blocks-desktop-bnpl-header-search
- Registry
- npm
What is MAL-2026-12927?
MAL-2026-12927 is a malicious package in bnpl-blocks-desktop-bnpl-header-search, published on 5 Aug 2026.
Official description
On require of the package, index.js loads adapter.js whose top-level main() constructs Cloudflare Workers hostnames (oob-worker.cf10{0-3}-.workers.dev) and a DNS-TXT discovery fallback (.dl.wel1.ru) via array-join string splitting, downloads a platform-specific binary, writes it to a temp path under disguised OS-diagnostic filenames (dotnet_diag.exe /.cache_), chmods it 0755, and spawns it detached via spawn("/bin/sh",["-c", filePath+" &"]) or cmd /c start /b. A second variant of the same drop/chmod/spawn chain is present in lib/telemetry.js, using Buffer.from(chunks,"base64") to reconstruct payload bytes. The package presents itself as an analytics/telemetry component (stamp file.analytics_state, DISABLE_TELEMETRY opt-out shim) but its declared purpose is a BNPL header-search UI block, which has no legitimate need to execute unsigned remote binaries. The endpoint obfuscation, cover-story naming, DNS-TXT censorship-evasion fallback, and disguised on-disk artifacts are characteristic of a hostile dropper.
What should I do about MAL-2026-12927?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.