Which versions of libpesh are malicious?

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

How do I remediate libpesh if I installed it?

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

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

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

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

Malicious package

libpeshPyPI

libpesh is a confirmed malicious PyPI package (MAL-2024-5321) 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 libpesh (PyPI)

MAL-2024-5321

Immediate action

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

pip uninstall libpesh

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

3e9e2ca6e63852d1dafe8225e5db265d303a2bd6ff42feb9f225d04bd231d433

63dd9eaafd1f9e2a1f2ebbcc13536a28813ef2f55e602e845797b92292837a83

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for libpesh (version 0.1).
If you installed it — respond
Remove libpesh 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 libpesh 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. libpesh 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-04103RLUA-2024-08467

References

blog.reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

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