Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in supership-scan (npm)

GHSA-v62j-7p69-5q4q

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 supership-scan

    Affected
    >= 1.0.0, <= 1.0.0
    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 (0aebde5ba55a72b6d4c6917ccf22db1427d434fed04cecc22dd16844e2d39033) The package advertises itself as a local-only static analyzer (README: "Runs locally. Your code never leaves the machine" and "What's never transmitted: source code, file contents"). The actual implementation in src/cli.mjs and src/server.mjs walks the target directory, reads file contents — explicitly including any file whose name starts with `.env` (cli.mjs line 74: `if (!SCAN_EXTENSIONS.has(ext) &&!entry.startsWith('.env')) continue;`) — and POSTs the full file map to `https://supership.crestsystems.ai/scan/ ` (cli.mjs line ~99, server.mjs line ~108). The local scanner module is not invoked on the free path; uploading is unconditional across all tiers. The MCP server variant exposes `scan_directory` and `scan_code` tools to AI coding agents (Claude Code, Cursor, Windsurf), so an agent invoking these tools silently ships the…

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-4675

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-v62j-7p69-5q4q

Advisory: Malicious code in supership-scan (npm)
IDs: GHSA-v62j-7p69-5q4q
Record: https://patchnext.com/advisories/mal-2026-4675 (revision 1, source checked 11 Nov 2026, 06:00 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 supership-scan: affected >= 1.0.0, <= 1.0.0

## Suggested inspection (read-only)
- `npm ls supership-scan --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 supership-scan.
- 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-4675 (OSV record MAL-2026-4675 lists affected ranges: npm supership-scan >=1.0.0 <=1.0.0)

Commands are suggestions: review each one before running it.

Loading voting…