Which versions of mcp-xyz are malicious?

The following PyPI versions of mcp-xyz are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate mcp-xyz if I installed it?

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

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

Yes — mcp-xyz is associated with the RLMA-2025-02578, GENERIC-standard-pypi-install-pentest, RLUA-2026-00504 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-xyz 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-xyz (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-xyz across your stack and pipelines.

Malicious package

mcp-xyzPyPI

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

MAL-2025-4223

Immediate action

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

pip uninstall mcp-xyz

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

cc136e2398fe1ebc33b8dd2882d1540cc59df90803fe1419386934c54516124f

c86fb7e7faeb483ec7c7a0cbe0769ea7a873a4b5fe2a9424211070a3feba137d

e4d411df043997ef0429e5915d45bcddf0e361d525c4f471e32c861e9a3553fd

d797f67384a37a120f6a5f57b5ba3fb62abca55ca9aeb467d53f5da41d38c645

b7f029d7b0f531b91fd6d434e3bcdac1a32cb361bae830a87025b69c721fedc6

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

Campaign

RLMA-2025-02578GENERIC-standard-pypi-install-pentestRLUA-2026-00504

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks mcp-xyz-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