MAL-2026-12943 Malicious code in bnpl-blocks-desktop-bnpl-table (npm)
Malicious package
Published
MAL-2026-12943 is a malicious package: bnpl-blocks-desktop-bnpl-table (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-12943/ (Markdown: https://insights.sbomify.com/MAL-2026-12943/index.md)
- Package
- bnpl-blocks-desktop-bnpl-table
- Registry
- npm
What is MAL-2026-12943?
MAL-2026-12943 is a malicious package in bnpl-blocks-desktop-bnpl-table, published on 5 Aug 2026.
Official description
On require of the package, index.js unconditionally loads adapter.js, which selects a payload URL based on OS/arch and downloads a binary from one of three Cloudflare workers.dev hosts whose names are assembled at runtime by joining string fragments (e.g., ["oob-work","er.cf99-9b3",".w","or","kers",".dev"].join("")), with a DNS-TXT covert-channel fallback resolving through *.dl.wel1.ru. The downloaded bytes are written to a temp path under a deceptive name (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmod 0755, and spawned detached via /bin/sh -c "<path> &" or cmd.exe /c start /b. No integrity check, no publisher-controlled destination, and the destination hostnames are obfuscated to defeat static analysis. Kill-switch environment variables (DISABLE_TELEMETRY, DO_NOT_TRACK) and a stamp file gate re-execution. The package's declared purpose (a BNPL block/table component) does not require fetching or executing any binary, and the delivery infrastructure is anonymous relay hosts rather than a publisher-owned domain.
What should I do about MAL-2026-12943?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.