Vulnerability
Malicious code in mcp-server-redis (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c94a122c1dd231888bc72b52cbef5dbdd793d2680f7e7e36385bd06e07dc20fd) Package claims the unscoped name `mcp-server-redis` to intercept `npx mcp-server-redis` invocations intended for the legitimate MCP Redis server ecosystem. `package.json` declares `scripts.postinstall: node index.js`, so on `npm install` the package automatically executes index.js, which collects host identifiers via `os.hostname()`, `os.platform()`, `process.cwd()`, `process.env.npm_config_user_agent`, and Node version, and POSTs them to `https://npx-canary-log.vulnerable-live.workers.dev/log` (hardcoded at index.js:16). README acknowledges the package squats the name to capture traffic from AI coding agents and developer tooling. Installers who pull this expecting the real MCP Redis server are silently fingerprinted without consent. Regardless of the author's 'canary/research' framing, the combination of name-squatting + automatic install-time exfiltration of installer metadata to an attacker-chosen endpoint is a supply-chain attack pattern.
No CVSS base score from NVD or GHSA yet. NVD typically scores within 24–72 hours of publication; GHSA usually within a day for OSS-flagged CVEs. Last record update .
For interim severity, fall back on KEV / EXPLOIT signals and the EPSS percentile (lower panel). Re-check this CVE after one cron tick — the score lands automatically when the source publishes.
FIRST.org publishes EPSS daily. Coverage isn't universal — pre-disclosure CVEs and reserved IDs don't carry an EPSS score until at least one exploitation signal lands. Score will appear within 24 hours of the next EPSS pull.
No exploitation, limited impact or prevalence