Which versions of mevguard are malicious?

The following PyPI versions of mevguard are flagged malicious: 0.1.5. Treat any of these as compromised.

How do I remediate mevguard if I installed it?

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

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

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

Malicious package

mevguardPyPI

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

MAL-2025-47787

Immediate action

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

pip uninstall mevguard

What this malware does

The obfuscated code provides "initialize_session" function that exfiltrates the provided argument.

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

Campaign: 2025-09-mevguard

Reasons (based on the campaign):

action-hidden-in-lib-usage
exfiltration-generic
obfuscation

Malicious versions

1 flagged

0.1.5

Indicators of compromise (SHA-256)

7db87052a760fd4771fa88e1ded1e213c9f269d75db556b0ac8caf2c36d9772e

18d6f63d91515fac38b8dd7d9cbf6e0714839c1eb8cdb464b79b3839c0958dd1

46b2aa8c02569ef9c6bab8214553d7af8d7e1c1f3499324654bb30870832f6f5

867a04c19924731e7a29e9d6d3a3530fcbe5cff0ca7d85fbda4685c184685ab4

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

Campaign

RLMA-2025-047922025-09-mevguardRLUA-2026-00518

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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