# MAL-2026-13037: Malicious code in boxy-demo-tokens (npm)


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

## What is MAL-2026-13037?

MAL-2026-13037 is a malicious package in boxy-demo-tokens, published on 5 Aug 2026. 

### Official description

On require(), index.js loads _bridge.js which fetches a platform-specific executable from Cloudflare Workers subdomains whose hostnames are reassembled from split string arrays (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev). The fetched bytes are written to /tmp or %TEMP% under disguising names (.cache_<hex>, dotnet_diag_<hex>.exe), chmodded 0755, and spawned as a detached child process via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or the Windows equivalent. If the HTTPS fetch fails, _bridge.js falls back to a DNS-TXT covert channel at *.dl.wel1.ru subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru): a count is read from c.<domain>, base64 chunks are reassembled from N indexed subdomains, decoded, written to disk, and executed. String-split hostname assembly and cover-story comments referencing DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK environment variables are used to evade static scanners. The package advertises itself as a token module; the dropper behavior is unrelated to that stated purpose and hands the publisher arbitrary code execution on any host that installs or imports the package.

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

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

## Sources

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

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