Which versions of hahabott are malicious?

The following PyPI versions of hahabott are flagged malicious: 1.20.1, 1.20.6, 1.20.7, 1.20.8, 1.20.9, 1.29.1, 1.29.3. Treat any of these as compromised.

How do I remediate hahabott if I installed it?

hahabott is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed hahabott — how do I know if it already compromised me?

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

Yes — hahabott is associated with the 2025-07-hahabott 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 hahabott across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hahabott (7 malicious versions).

Malicious package

hahabottPyPI

Advisory published Jul 19, 2025Updated Dec 12, 2025

hahabott is a confirmed malicious PyPI package (MAL-2025-191746) that steals credentials and exfiltrates sensitive data (malicious versions 1.20.1, 1.20.6, 1.20.7…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hahabott (PyPI)

MAL-2025-191746

Immediate action

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

pip uninstall hahabott

What this malware does

If run as module, it attempts to automatically destroy user's and system's files. Some versions also exfiltrate them.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-07-hahabott

Reasons (based on the campaign):

files-exfiltration
destructive-actions

Malicious versions

7 flagged

1.20.11.20.61.20.71.20.81.20.91.29.11.29.3

Indicators of compromise (SHA-256)

4e54f2e63a559a138a6ad08357607009c1725de084e8a406a268d67b1ca3e99b

89ed03d9e80d4ef62c54087a12177f795e478b1b5e5a8af69ef4e4740e102186

7b41adec259822ebbf3bceb10f2898f8ec0b31fdf7505dea7efea4e2371c3e71

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for hahabott (7 malicious versions).
If you installed it — respond
hahabott is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If hahabott 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. hahabott on PyPI has been identified as a malicious package (versions 1.20.1, 1.20.6, 1.20.7, 1.20.8, 1.20.9, 1.29.1, 1.29.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-07-hahabott

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks hahabott-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database