# MAL-2026-13298: Malicious code in dolyame-boxy-block (npm)


- **Type:** Malicious package
- **Package:** `dolyame-boxy-block` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-13298?

MAL-2026-13298 is a malicious package in dolyame-boxy-block, published on 5 Aug 2026. 

### Official description

dolyame-boxy-block@35.5.2 ships a `_runtime.js` module that is unconditionally required from `index.js` at load time. On import, `_runtime.js` reconstructs attacker-controlled hostnames from split string arrays (e.g. `["oob-wor","ker.cf99-9b3.workers.dev"].join("")` producing `oob-worker.cf99-9b3.workers.dev`, and similar for `oob-worker.cf100-416.workers.dev`, `oob-worker.cf101-adf.workers.dev`, `oob-worker.cf103-070.workers.dev`), performs an `https.get` to a platform-specific endpoint, writes the returned bytes to `/var/tmp` or `%TEMP%` under a decoy filename (`.cache_<rand>` on POSIX, `dotnet_diag_<rand>.exe` on Windows), `chmod 0755`s the file, and spawns it detached via `/bin/sh -c "<path> &"` or `cmd.exe` with `stdio:"ignore"` and `.unref()`. If the HTTPS mirrors fail, a DNS-TXT covert channel under `sdk.dl.wel1.ru` / `ext.dl.wel1.ru` / `pkg.dl.wel1.ru` / `net.dl.wel1.ru` retrieves a base64-encoded payload chunked across multiple TXT records (`c.<domain>`, `0.<domain>`, `1.<domain>`...), reassembles it, and executes it through the same write-and-spawn sink. The advertised purpose ("boxy block" UI library) does not match the shipped behavior; the hostnames are obfuscated to evade static string search; the fetched binary is unpinned, unhashed, and unsigned. Any consumer that `require()`s or `import`s the package triggers full-host remote code execution.

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

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-13298 is a malicious package: dolyame-boxy-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-13298/ (Markdown: https://insights.sbomify.com/MAL-2026-13298/index.md)
```

## Sources

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

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