Which versions of prooxify are malicious?

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

How do I remediate prooxify if I installed it?

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

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

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

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

Malicious package

prooxifyPyPI

prooxify is a confirmed malicious PyPI package (MAL-2024-5566) 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 prooxify (PyPI)

MAL-2024-5566

Immediate action

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

pip uninstall prooxify

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

a336ce72ed09d4435ad0feceb6fb9fcde09e552b9de90e7591fcbf0f83b0f7ca

7209308fa8886c93e5638b99cf391a465f9b0e756087d578012773dfc1892311

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for prooxify (version 1.0).
If you installed it — respond
Remove prooxify 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 prooxify 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. prooxify 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-04348RLUA-2024-08778

Credits

ReversingLabs · finder

Detect & block this

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