Which versions of pyobfgood are malicious?

The following PyPI versions of pyobfgood are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate pyobfgood if I installed it?

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

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

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

Search your lockfiles and build artifacts for pyobfgood (4 malicious versions).

Malicious package

pyobfgoodPyPI

pyobfgood is a confirmed malicious PyPI package (MAL-2024-5748) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pyobfgood (PyPI)

MAL-2024-5748

Immediate action

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

pip uninstall pyobfgood

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

886cfb2c21defe38aae63febbe1824b35e811a6378852cbe67018a06e3f68779

f6b7bdfc5e8f1a67a90929b781f1cf0940ef16a70e0afdaa5c054b0787af39ef

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04542RLUA-2024-08973

References

Credits

ReversingLabs · finder

Detect & block this

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