Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in dsh-vm-tester (npm)

GHSA-84fw-gj66-p5v3

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm dsh-vm-tester

    Affected
    >= 0.1.3, <= 0.1.3>= 0.1.2, <= 0.1.2>= 0.1.4, <= 0.1.4
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (9a0402f4d4ed70da37124eb7d4e1cfd585f2b9afbb63cca44436692a3d21d090) 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.

Source: ghsa-malware…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record MAL-2026-18345

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18345

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-84fw-gj66-p5v3

Advisory: Malicious code in dsh-vm-tester (npm)
IDs: GHSA-84fw-gj66-p5v3
Record: https://patchnext.com/advisories/mal-2026-18345 (revision 2, source checked 30 Oct 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm dsh-vm-tester: affected >= 0.1.3, <= 0.1.3; >= 0.1.2, <= 0.1.2; >= 0.1.4, <= 0.1.4

## Suggested inspection (read-only)
- `npm ls dsh-vm-tester --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dsh-vm-tester.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18345 (OSV record MAL-2026-18345 lists affected ranges: npm dsh-vm-tester >=0.1.3 =0.1.2 =0.1.4 <=0.1.4)

Commands are suggestions: review each one before running it.

Loading voting…