Which versions of libcrypt are malicious?

The following PyPI versions of libcrypt are flagged malicious: 1.0.0, 1.2.0. Treat any of these as compromised.

How do I remediate libcrypt if I installed it?

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

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

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

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

Malicious package

libcryptPyPI

libcrypt is a confirmed malicious PyPI package (MAL-2024-5310) that executes malicious code on install (malicious versions 1.0.0, 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libcrypt (PyPI)

MAL-2024-5310

Immediate action

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

pip uninstall libcrypt

Malicious versions

2 flagged

1.0.01.2.0

Indicators of compromise (SHA-256)

e92cae63253bce60835118cd3156469d1554928fa3f42ea9b954773b4230086c

1519eab157d75801e86496445dc53ed0f29c5b165f5b394cb3c864b7a715ab96

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04092RLUA-2024-08456

Credits

ReversingLabs · finder

Detect & block this

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