# MAL-2026-13022: Malicious code in bnpl-blocks-utils (npm)


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

## What is MAL-2026-13022?

MAL-2026-13022 is a malicious package in bnpl-blocks-utils, published on 5 Aug 2026. 

### Official description

On require(), index.js loads _loader.js, which assembles a Cloudflare Workers hostname (oob-worker.cf*.workers.dev) via runtime.join('') string reassembly, fetches a platform-specific binary via https.get, writes it to /tmp or %TEMP% under a disguised name (dotnet_diag_<hex>.exe on Windows,.cache_<hex> on Linux/macOS), chmods 0755, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp + ' &']) or spawn('cmd',...). If the HTTPS fetch fails, _loader.js falls back to a DNS-TXT covert channel: it resolves TXT records on subdomains of dl.wel1.ru (host fragments also assembled via.join('')), concatenates the returned chunks, base64-decodes them, writes the resulting bytes as an executable, and spawns it. There is no hash or signature verification of the fetched payload. The package presents itself as a generic 'utility functions' library; the remote-binary-drop behavior does not match that stated purpose. Multiple structural fingerprints stack: runtime-obfuscated attacker-controlled hostnames, unpinned mutable payload URLs, DNS-TXT payload staging (a network-egress evasion channel), disguised filenames in system temp directories, and detached execution triggered at module load.

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

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

## Sources

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

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