# MAL-2026-12079: Malicious code in volna-boxy-di-test (npm)


- **Type:** Malicious package
- **Package:** `volna-boxy-di-test` (npm)
- **Published:** 5 Aug 2026
- **Also known as:** GHSA-2gq5-r78g-rrmq

## What is MAL-2026-12079?

MAL-2026-12079 is a malicious package in volna-boxy-di-test, published on 5 Aug 2026. 

### Official description

On require, index.js loads _compat.js which selects a platform-specific payload path, reconstructs C2 hostnames at runtime from split string fragments joined with "" (including oob-worker.cf10*-*.workers.dev variants and a *.dl.well1.site DNS TXT chunked-base64 fallback), fetches unpinned unhashed bytes over HTTPS, writes them to /tmp or %TEMP% under disguising names such as.cache_<hex> and dotnet_diag_<hex>.exe, chmods 0755 on Unix, and spawns the binary detached via /bin/sh -c or cmd. The User-Agent is spoofed to node-fetch/2.6 to blend with legitimate traffic, a TTL flag file (.analytics_state) suppresses re-execution, and env gates (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) plus cover-story comments ("telemetry", "analytics", "Skip in CI") mask the dropper. The package presents itself as a test harness; the fetched code, the hosts, and the disguised filenames do not match that stated purpose.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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

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

## Sources

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

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