Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in dsh-redteam-mode (npm)

GHSA-r4m9-8735-g966

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-redteam-mode

    Affected
    >= 0.15.2, <= 0.15.2
    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 (4b10e8cb5b42b044dde881818592b20e43d2166d6641bd657bf90c2aa5a0c0a2) Package name and shipped file names (score-rules.js, report-replay.js, store-core.js, tools.js, client.js) describe an offensive-security / red-team mode helper. Pattern matches fire on co-occurrence of curl invocations and HTTP GET/POST calls across several library files, which is expected shape for pentest tooling that constructs example requests, replays reports, and scores rules. No lifecycle script-driven install-time execution, no hardcoded exfiltration endpoint, no credential-store or home-directory secret enumeration, and no obfuscated remote fetch were identified in the evidence. The curl and POST tokens appear as part of library methods callers must explicitly invoke rather than install-time or import-time side effects. Offensive-security libraries are a legitimate category and installing them does not by itself attack…

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

    Published from osv record MAL-2026-18366

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-r4m9-8735-g966

Advisory: Malicious code in dsh-redteam-mode (npm)
IDs: GHSA-r4m9-8735-g966
Record: https://patchnext.com/advisories/mal-2026-18366 (revision 1, 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-redteam-mode: affected >= 0.15.2, <= 0.15.2

## Suggested inspection (read-only)
- `npm ls dsh-redteam-mode --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-redteam-mode.
- 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-18366 (OSV record MAL-2026-18366 lists affected ranges: npm dsh-redteam-mode >=0.15.2 <=0.15.2)

Commands are suggestions: review each one before running it.

Loading voting…