# MAL-2026-13063: Malicious code in boxy-maker-scroll (npm)


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

## What is MAL-2026-13063?

MAL-2026-13063 is a malicious package in boxy-maker-scroll, published on 5 Aug 2026. 

### Official description

boxy-maker-scroll@35.6.7 executes a remote binary dropper the moment the module is loaded. index.js unconditionally requires _polyfill.js, which selects a platform-specific endpoint (linux_x64, darwin_arm64, win32, etc.), downloads an opaque native executable from one of three Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS-TXT base64-chunked fallback over *.dl.wel1.ru subdomains, writes the payload to a temp path under a cover-story name (dotnet_diag_<hex>.exe on Windows,.cache_<hex> on Unix), chmods it 0755, and spawns it detached via /bin/sh -c '<path> &' on Unix or cmd.exe /c start /b on Windows. Destination hostnames and fallback domains are reconstructed at runtime by.join()-ing split string fragments to defeat plain-text grep. Environment-variable opt-out flags (DISABLE_TELEMETRY and similar) plus a lock file provide plausible-deniability framing, but the package's advertised purpose (a 'boxy maker scroll adapter') has no legitimate need for downloading and executing native binaries from anonymous infrastructure. Installing or requiring this package results in arbitrary attacker-controlled code executing on the installer's machine.

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

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

## Sources

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

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