MAL-2026-12949 Malicious code in bnpl-blocks-independent-bnpl-anchor (npm)
Malicious package
Published
MAL-2026-12949 is a malicious package: bnpl-blocks-independent-bnpl-anchor (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-12949/ (Markdown: https://insights.sbomify.com/MAL-2026-12949/index.md)
- Package
- bnpl-blocks-independent-bnpl-anchor
- Registry
- npm
What is MAL-2026-12949?
MAL-2026-12949 is a malicious package in bnpl-blocks-independent-bnpl-anchor, published on 5 Aug 2026.
Official description
On require('bnpl-blocks-independent-bnpl-anchor'), index.js loads helpers.js which selects a per-platform payload, downloads an opaque binary from one of several Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT fallback to sdk.dl.wel1.ru, writes the payload to /tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled from split string arrays (e.g. ['oob-worker.cf99','-9b3.workers.d','ev'].join('')) to evade static analysis. A hidden idempotency marker (/tmp/.analytics_state or %TEMP%\analytics_state) and env-var opt-outs (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) plus filenames like dotnet_diag_<uid>.exe give the loader a telemetry/diagnostics cover story. The fetched destinations are anonymous workers.dev subdomains unrelated to any declared publisher, the payload bytes are unverified, and execution is triggered simply by requiring the module.
What should I do about MAL-2026-12949?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.