mcp-server-redis
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-wrqr-prmr-6x32
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
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.
Source: ghsa-malware (ce279b84c312d93a9b0832260c5f2b9397a8fbcfe33b439bd8d016698eebf94b)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0