Which versions of colarg are malicious?

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

How do I remediate colarg if I installed it?

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

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

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

Search your lockfiles and build artifacts for colarg (2 malicious versions).

Malicious package

colargPyPI

colarg is a confirmed malicious PyPI package (MAL-2024-4907) that executes malicious code on install (malicious versions 0.1, 0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in colarg (PyPI)

MAL-2024-4907

Immediate action

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

pip uninstall colarg

Malicious versions

2 flagged

0.10.2

Indicators of compromise (SHA-256)

6986e7936463615138d64adc0c366eff1ed1b8d233e272f684a88e5bb3bcbb58

aad9c9040afe5bbb4e1168dd6b72e0cdd60b0dc3ffdc467dd9c55afc3be449f3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03687RLUA-2024-07978

Credits

ReversingLabs · finder

Detect & block this

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