Which versions of mcp-server-redis are malicious?

The following npm versions of mcp-server-redis are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate mcp-server-redis if I installed it?

mcp-server-redis is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed mcp-server-redis — how do I know if it already compromised me?

If mcp-server-redis was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is mcp-server-redis part of a known attack campaign?

Yes — mcp-server-redis is associated with the IN-MAL-2026-005229, IN-MAL-2026-005230, IN-MAL-2026-005906, IN-MAL-2026-005905 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find mcp-server-redis across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-server-redis (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-server-redis across your stack and pipelines.

Malicious package

mcp-server-redisnpm

Malicious code in mcp-server-redis (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5482

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall mcp-server-redis

What this malware does

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.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

2c31b47d009efb7e10d0b41e71923fcfefa90a45895db0ec02bc6c8f1fee1c86

f4a4d371479bb5a292f632f9afc8661c13142c51f347d3013cc5dceca8ce46ab

b6d87b7f9e47dd6abfb85badcb819ef44b8f6a3e8fa20439709e7bf7606b3532

c94a122c1dd231888bc72b52cbef5dbdd793d2680f7e7e36385bd06e07dc20fd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-server-redis (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-server-redis across your stack and pipelines.
If you installed it — respond
mcp-server-redis is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If mcp-server-redis was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks mcp-server-redis before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. mcp-server-redis on npm has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005229IN-MAL-2026-005230IN-MAL-2026-005906IN-MAL-2026-005905

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mcp-server-redis-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring