Which versions of m5tlprovetomegz are malicious?

The following PyPI versions of m5tlprovetomegz are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate m5tlprovetomegz if I installed it?

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

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

Yes — m5tlprovetomegz is associated with the RLMA-2025-04193, 2025-07-m5tlprovetomegz, RLUA-2026-00485 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 m5tlprovetomegz 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 m5tlprovetomegz (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging m5tlprovetomegz across your stack and pipelines.

Malicious package

m5tlprovetomegzPyPI

Malicious code in m5tlprovetomegz (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-41699

Immediate action

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

pip uninstall m5tlprovetomegz

What this malware does

Importing the module starts downloading and executing a file recognized as malicious by AVs

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

Campaign: 2025-07-m5tlprovetomegz

Reasons (based on the campaign):

malware
Downloads and executes a remote executable.

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

0d9b7dc8331eb2997090234ca73a4aa5d69579bc6ac6bcd3f4621a80afc68377

687b85e4f704918e8e36ad13bfeba2bed752cfca080c5467343c7e35da45fded

41041b6e55e23e7b8d40be5bb95a75fdba5b64cb9524c86054deabcd2177e459

e89a518d28a92f592fdc055887892c42b310aa627ecf14f0370b0f2bd4844d26

285b3e80ec0896f9baaa87380294109a6781eab577204546cdb812441ffdec35

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

Campaign

RLMA-2025-041932025-07-m5tlprovetomegzRLUA-2026-00485

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks m5tlprovetomegz-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