MAL-2026-12971 Malicious code in bnpl-blocks-independent-bnpl-table (npm)
Malicious package
Published
MAL-2026-12971 is a malicious package: bnpl-blocks-independent-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-12971/ (Markdown: https://insights.sbomify.com/MAL-2026-12971/index.md)
- Package
- bnpl-blocks-independent-bnpl-table
- Registry
- npm
What is MAL-2026-12971?
MAL-2026-12971 is a malicious package in bnpl-blocks-independent-bnpl-table, published on 5 Aug 2026.
Official description
Requiring bnpl-blocks-independent-bnpl-table transitively loads compat.js, which auto-invokes a start() routine at module load. The routine downloads a platform-specific native executable over HTTPS from Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS TXT fallback under *.dl.wel1.ru for base64-encoded payload delivery. Hostnames are reconstructed at runtime by joining split string fragments to hide them from casual inspection. The downloaded binary is written to /tmp (Unix) as a hidden file named.cache<hex> or to %TEMP% (Windows) under a masquerading name like dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe. A stamp file named.analytics_state and 'telemetry'/'graceful degradation' labels form a cover story. The delivered binary is opaque, unpinned, unverified, and the fetch destinations do not match the package publisher and are unrelated to the package's stated BNPL-table purpose.
What should I do about MAL-2026-12971?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.