Which versions of libig are malicious?

The following PyPI versions of libig are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate libig if I installed it?

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

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

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

Search your lockfiles and build artifacts for libig (version 0.1).

Malicious package

libigPyPI

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

Malicious code in libig (PyPI)

MAL-2024-5319

Immediate action

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

pip uninstall libig

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

55007ae29dabb83972efddb06c9173ef7a51cff0ceb3e5a6edaf871b6735f067

ba15f7dbed0aa76732e9c0b046ef24958d6d51f36757d58b9eea594cee7a703e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04101RLUA-2024-08465

References

Credits

ReversingLabs · finder

Detect & block this

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