Which versions of zproxy are malicious?

The following PyPI versions of zproxy are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate zproxy if I installed it?

Remove zproxy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed zproxy — how do I know if it already compromised me?

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

Yes — zproxy is associated with the RLMA-2024-05064, RLUA-2024-09583 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 zproxy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zproxy (version 1.0).

Malicious package

zproxyPyPI

zproxy is a confirmed malicious PyPI package (MAL-2024-6260) that executes malicious code on install (malicious version 1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zproxy (PyPI)

MAL-2024-6260

Immediate action

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

pip uninstall zproxy

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

d71c3dff3b92802aa1cb79fdf039810ba8aa7b96aa3678d4c7548dae604d95ac

ab640b8f6ca3b29fefd09b2ac1577f6890fd2f0a5814f2f1a56e7011983f5be8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zproxy (version 1.0).
If you installed it — respond
Remove zproxy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If zproxy 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. zproxy on PyPI has been identified as a malicious package (version 1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05064RLUA-2024-09583

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks zproxy-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database