Which versions of py-co4d are malicious?

The following PyPI versions of py-co4d are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate py-co4d if I installed it?

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

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

Yes — py-co4d is associated with the RLMA-2024-04369, RLUA-2024-08802 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 py-co4d across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for py-co4d (version 1.0.0).

Malicious package

py-co4dPyPI

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

Malicious code in py-co4d (PyPI)

MAL-2024-5587

Immediate action

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

pip uninstall py-co4d

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

082bfae1990d47bcb7c4fa0ba079a9438fa7f991bff5c5cb310bcb986830d92a

4127d6a294ea7a036c74d2adcb2519ddc08925c45e2b634c027046aa6241a1f8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for py-co4d (version 1.0.0).
If you installed it — respond
Remove py-co4d 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 py-co4d 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. py-co4d on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04369RLUA-2024-08802

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks py-co4d-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