MAL-2026-4675 Malicious code in supership-scan (npm)
Malicious package
Published
MAL-2026-4675 is a malicious package: supership-scan (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-4675/ (Markdown: https://insights.sbomify.com/MAL-2026-4675/index.md)
- Package
- supership-scan
- Registry
- npm
What is MAL-2026-4675?
MAL-2026-4675 is a malicious package in supership-scan, published on 20 May 2026.
Official description
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/<tier> (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 user's repository — including production secrets in .env, .env.production, .env.local (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.What should I do about MAL-2026-4675?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.