Which versions of libari are malicious?

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

How do I remediate libari if I installed it?

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

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

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

Search your lockfiles and build artifacts for libari (3 malicious versions).

Malicious package

libariPyPI

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

Malicious code in libari (PyPI)

MAL-2024-5308

Immediate action

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

pip uninstall libari

Malicious versions

3 flagged

0.10.20.3

Indicators of compromise (SHA-256)

8b16b2c517d3a3690e8b3d338c3872b90cd158a4d6de4f8da063b15c7213f026

90c1dcfbd5598db371cc458a1008d2d1ce644cb99fd19895605928e049c3cc9c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04090RLUA-2024-08454

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

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