Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

mcp-runcmd-serverPyPI

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

MAL-2025-191788
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall mcp-runcmd-server

What this malware does

Package starts a reverse shell to a hardcoded location

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-10-mcp-runcommand-server

Reasons (based on the campaign):

  • The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

2 flagged
1.02.0

Indicators of compromise (SHA-256)

970f8eef061302ee1741f2441b75587c89ba4c03dc2b8957aa0153487b364022
2e5608c421ba44a3a2e20b924bd3399d6452dba66e7aea10a0fcdc8044f5a996
22017cb0a5e5e8de99e25dbbd8b3ff3546d3a61d56aec583f6545473ed133194

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-runcmd-server (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-runcmd-server across your stack and pipelines.

  2. If you installed it — respond

    mcp-runcmd-server 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.

  3. Did it already run?

    If mcp-runcmd-server 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.

  4. How O3 protects you

    O3 blocks mcp-runcmd-server 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-runcmd-server on PyPI has been identified as a malicious package (versions 1.0, 2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-10-mcp-runcommand-server

References

Credits

  • Kamil Mańkowski (kam193)

Detect & block this

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

mcp-runcmd-server (PyPI) malicious package — MAL-2025-191788 | O3 Security