Which versions of mcp-runcommand-server2 are malicious?

The following PyPI versions of mcp-runcommand-server2 are flagged malicious: 1.0.6. Treat any of these as compromised.

How do I remediate mcp-runcommand-server2 if I installed it?

mcp-runcommand-server2 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-runcommand-server2 — how do I know if it already compromised me?

If mcp-runcommand-server2 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-runcommand-server2 part of a known attack campaign?

Yes — mcp-runcommand-server2 is associated with the RLMA-2025-05620, 2025-10-mcp-runcommand-server, RLUA-2026-00503 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-runcommand-server2 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-runcommand-server2 (version 1.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-runcommand-server2 across your stack and pipelines.

Malicious package

mcp-runcommand-server2PyPI

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

MAL-2025-191648

Immediate action

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

pip uninstall mcp-runcommand-server2

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

1 flagged

1.0.6

Indicators of compromise (SHA-256)

27ac8c6aa1983e37941dd0e54bf06040a0b3274c459e304bc9bb09a22127d3b5

384331780fb13cb123275da0b3e4d52ef2acf5beabb5d90d810624fe4099cd7a

36fb61d44529c380f204d5a210017989695ef39df6adfce7ccfb08e48a17b594

73107322dee0ccc3e592daa461014299c4daac49c933c8323b0e9edb26af23bb

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-runcommand-server2 (version 1.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-runcommand-server2 across your stack and pipelines.
If you installed it — respond
mcp-runcommand-server2 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-runcommand-server2 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-runcommand-server2 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-runcommand-server2 on PyPI has been identified as a malicious package (version 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-056202025-10-mcp-runcommand-serverRLUA-2026-00503

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks mcp-runcommand-server2-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