Which versions of pydistoolhebs are malicious?

The following PyPI versions of pydistoolhebs are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pydistoolhebs if I installed it?

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

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

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

Search your lockfiles and build artifacts for pydistoolhebs (version 0.0.1).

Malicious package

pydistoolhebsPyPI

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

Malicious code in pydistoolhebs (PyPI)

MAL-2024-5704

Immediate action

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

pip uninstall pydistoolhebs

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

13916f2e1ca455e25b7b479b37249f5a3e25b75f7a2a62858c14d1ddb0f455f0

d78dd5d881f1076e31f81aa712835f82dfb08c7f899df968c2c4ce940466b196

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04487RLUA-2024-08924

Credits

ReversingLabs · finder

Detect & block this

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