Vulnerabilities

Security incident · MAL-2026-4675

Malicious code in supership-scan (npm)

Published May 20, 2026 · catalog updated Nov 10, 2026 · Malicious code in supership-scan

Last checked Nov 10, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for MAL-2026-4675. A missing EPSS score is not a low risk. Compare Malicious code in supership-scan with the linked advisory before you change production.

Severity

Unknown—

Known exploitation

Not in CISA/VulnCheck KEV

EPSS

Awaiting synchronization with FIRST

Remediation

Advisory link

Affected products

npm supership-scan

--- _-= 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 (cli.mjs line 74: ) — and POSTs the full file map to (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 and tools to AI coding agents (Claude Code, Cursor, Windsurf), so an agent invoking these tools silently ships the user's repository — including production secrets in , , (DATABASE_URL, API keys, JWT secrets, cloud credentials) — to the author's endpoint without consent. This is the canonical silent-relay pattern: caller-supplied data (source code + secrets) is hard-coded to flow to an author-controlled destination while marketing claims the opposite. ## Source: ghsa-malware (0e482ca14e9c633ea9b8642c2f13acf558f7425f474f918ea95e2c46d56c6c0b) 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.