Malware in mem0-mcp-server npm package — full host compromise; rotate all secrets
Severity: critical · Patch status: no-fix-needed · Since 2026-11-16
GitHub's advisory database published GHSA-9hvg-j8mj-55xr on 2026-11-16, mirrored in OSV as MAL-2026-20011, classifying the npm package mem0-mcp-server as embedded malicious code (CWE-506). The advisory covers every version (= 0) and no fixed version exists. It says any machine that installed or ran the package should be treated as fully compromised, that every secret on it should be rotated from a different computer, and that removing the package may not remove what it installed. The npm registry now serves only a security-holding placeholder (0.0.1-security, published 2026-11-16) in place of the original package, so the original publisher and source repository are no longer visible there. The registry's release index still lists versions 1.0.0 to 2.0.0 published between 2026-03-14 and 2026-03-25. The npm download API reports 426 downloads in the 30 days to 2026-11-16, 2,187 since 2026-03-01, and 324 on 2026-11-16 itself. Mem0's own MCP server of the same name is a Python package on PyPI, archived upstream; it is not this npm package.
What to do
- Treat any machine with mem0-mcp-server installed or run as fully compromised; isolate it
- Rotate all secrets, keys and credentials stored on or accessible from affected machines, from a clean computer
- Remove the package and rebuild/reimage affected systems rather than trusting cleanup
- Audit systems and CI for installation of mem0-mcp-server and review logs for attacker activity
- Block/flag mem0-mcp-server in internal registries and dependency scanning
Sources
All live incidents on Threat Watch