# MAL-2026-18345: Malicious code in dsh-vm-tester (npm)


- **Type:** Malicious package
- **Package:** `dsh-vm-tester` (npm)
- **Published:** 27 Oct 2026
- **Also known as:** GHSA-84fw-gj66-p5v3

## What is MAL-2026-18345?

MAL-2026-18345 is a malicious package in dsh-vm-tester, published on 27 Oct 2026. 

### Official description

Package dsh-vm-tester 0.1.2 ships agent/tunnel-host.js, which imports Node's child_process module and performs HTTP GET operations. Keyword co-occurrence of child_process and HTTP primitives in a tunnel/agent-style script fired a pattern-match rule, but no traced code path demonstrates installer-side credential reads, environment-variable scraping, hardcoded attacker C2 destinations, or install-time execution of fetched content. The package has no lifecycle scripts invoking this file at install time; the behavior is reachable only when the agent/tunnel host is explicitly launched. The code shape is consistent with a legitimate VM-test tunneling agent that spawns processes and talks HTTP, but the destination endpoints and the data flowing to them have not been verified against first-party infrastructure.

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-18345?

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-18345 is a malicious package: dsh-vm-tester (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-18345/ (Markdown: https://insights.sbomify.com/MAL-2026-18345/index.md)
```

## Sources

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

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