Malware in mcp-server-redis
Malware was discovered in the npm package mcp-server-redis. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with mcp-server-redis installed or running is considered fully compromised.
- Ecosystems
- Attack vectors
- Affected entities
- mcp-server-redis
A critical malware incident was identified in the npm package mcp-server-redis. According to the GitHub Advisory (GHSA-wrqr-prmr-6x32), any system that has installed or executed this package should be treated as fully compromised.\n\nThe advisory recommends immediate action: all secrets and cryptographic keys stored on affected computers must be rotated from a different, uncompromised system. While the malicious package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nAffected users should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- mcp-server-redis
Remediation
- Immediately rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Remove the mcp-server-redis package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had this package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding affected systems from clean media if full compromise is suspected
Sources
- GitHub Advisory GHSA-wrqr-prmr-6x32 · GitHub Advisory Database
Cite this entry
"Malware in mcp-server-redis." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 20, 2026; last updated August 20, 2026. https://supplychainattack.org/incident/malware-in-mcp-server-redis-1r35se
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package