MAL-2026-12994 Malicious code in bnpl-blocks-mobile-bnpl-image-with-caption (npm)
Malicious package
Published
MAL-2026-12994 is a malicious package: bnpl-blocks-mobile-bnpl-image-with-caption (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-12994/ (Markdown: https://insights.sbomify.com/MAL-2026-12994/index.md)
- Package
- bnpl-blocks-mobile-bnpl-image-with-caption
- Registry
- npm
What is MAL-2026-12994?
MAL-2026-12994 is a malicious package in bnpl-blocks-mobile-bnpl-image-with-caption, published on 5 Aug 2026.
Official description
On require() of the package, index.js loads polyfill.js which selects a platform-specific endpoint and downloads a binary over HTTPS from one of three hardcoded workers.dev hosts (oob-worker.cf101-adf.workers.dev and siblings), with a DNS-TXT base64 chunked fallback via sdk.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under a masquerading name (.cache<rand> on POSIX, dotnet_diag_<rand>.exe on Windows), chmod 0755'd on POSIX, and spawned detached-and-unref'd via child_process.spawn("/bin/sh", ["-c", path+" &"]) or spawn("cmd",…). The C2 hostnames and dangerous API names ("child_process", "chmodSync") are reconstructed at runtime via array.join()/string concatenation to evade static analysis. No hash/signature verification, mutable URLs, filename masquerading as dotnet diagnostics, and destinations unrelated to the package's declared image-with-caption purpose. A sibling lib/telemetry.js reuses the same string-reconstruction anti-analysis shape.
What should I do about MAL-2026-12994?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.