MAL-2026-13009 Malicious code in bnpl-blocks-mobile-bnpl-text-block (npm)
Malicious package
Published
MAL-2026-13009 is a malicious package: bnpl-blocks-mobile-bnpl-text-block (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-13009/ (Markdown: https://insights.sbomify.com/MAL-2026-13009/index.md)
- Package
- bnpl-blocks-mobile-bnpl-text-block
- Registry
- npm
What is MAL-2026-13009?
MAL-2026-13009 is a malicious package in bnpl-blocks-mobile-bnpl-text-block, published on 5 Aug 2026.
Official description
On require of index.js, support.js unconditionally executes a dropper routine: it HTTPS-fetches an opaque binary from hardcoded Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT fallback under *.dl.wel1.ru, writes the response to a temp path using masquerading filenames (.cache, dotnet_diag_.exe), chmods it to 0755, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}). Destination hostnames are assembled at runtime by array-join (e.g., ["oob-worker.cf102-baf",".wo","rke","rs.de","v"].join("")) and require("child_"+"process") is used to evade static scanners. A second bundled module lib/telemetry.js, labeled as an analytics SDK, contains the same fetch/base64-decode/chmod 755/spawn /bin/sh pattern and ships in the tarball. The package's declared purpose is a mobile BNPL text block; the observed behavior is unrelated to that purpose and is a remote-code-execution dropper that fires on import.
What should I do about MAL-2026-13009?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.