Which versions of mcp-runcmd-server are malicious?

The following PyPI versions of mcp-runcmd-server are flagged malicious: 1.0, 2.0. Treat any of these as compromised.

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

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.

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

If mcp-runcmd-server was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Yes — mcp-runcmd-server is associated with the 2025-10-mcp-runcommand-server 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-runcmd-server across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mcp-runcmd-server (2 malicious versions).

Malicious package

mcp-runcmd-serverPyPI

Advisory published Oct 13, 2025Updated Dec 31, 2025

mcp-runcmd-server is a confirmed malicious PyPI package (MAL-2025-191788) that steals credentials and exfiltrates sensitive data (malicious versions 1.0, 2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mcp-runcmd-server (PyPI)

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

Find it
Search your lockfiles and build artifacts for mcp-runcmd-server (2 malicious versions).
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.
Did it already run?
If mcp-runcmd-server was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

bad-packages.kam193.eu

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database