# MAL-2026-12911: Malicious code in bnpl-blocks-desktop-bnpl-action-panel (npm)


- **Type:** Malicious package
- **Package:** `bnpl-blocks-desktop-bnpl-action-panel` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-12911?

MAL-2026-12911 is a malicious package in bnpl-blocks-desktop-bnpl-action-panel, published on 5 Aug 2026. 

### Official description

On require() of the package's main entry, _compat.js reconstructs Cloudflare Workers hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev) from split string fragments joined at runtime, downloads a platform-specific binary via https.get, writes it to a temp path disguised as a system file (`.cache_<hex>` on unix, `dotnet_diag_<hex>.exe` on Windows), chmods it 0755, and spawns it detached via `/bin/sh -c` on unix or `cmd /c start /b` on Windows. If the HTTPS fetch fails, the code falls back to a DNS-over-TXT channel querying chunked TXT records under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, base64-decodes the concatenated chunks, and uses the result as the executable payload. The `child_process` module is likewise obtained via `require("child_"+"process")` in a sibling telemetry file, and cover-story comments label the behavior as analytics/telemetry. The runtime string reconstruction of destinations, disguised filenames, detached-spawn pattern, and DNS-TXT egress-bypass channel are consistent with a load-time remote code execution dropper against any host that installs or imports this package.

## What should I do about MAL-2026-12911?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-12911 is a malicious package: bnpl-blocks-desktop-bnpl-action-panel (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-12911/ (Markdown: https://insights.sbomify.com/MAL-2026-12911/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-12911

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-12911/
Summaries are generated and may contain mistakes; the official description above is the record.