Which versions of pycrackhash are malicious?

The following PyPI versions of pycrackhash are flagged malicious: 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate pycrackhash if I installed it?

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

If pycrackhash was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is pycrackhash part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pycrackhash (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pycrackhash across your stack and pipelines.

Malicious package

pycrackhashPyPI

Malicious code in pycrackhash (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191832

Immediate action

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

pip uninstall pycrackhash

What this malware does

When using methods from the package, it downloads an obfuscated code from Github and puts it in multiple localisation. While it appears that this code is used to perform action user requested, deobfuscation reveals exfiltrating user's data instead.

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

Campaign: 2025-08-kertash

Reasons (based on the campaign):

exfiltration-generic
A Telegram webhook is used to send collected data.
obfuscation
action-hidden-in-lib-usage

Malicious versions

2 flagged

0.1.10.1.2

Indicators of compromise (SHA-256)

7019a9a9b0b31c8a2a4ed5bdf230e0bb7fc847b6f16efb3fbf87a75278f8a040

b3323afe460298d80a354497acdd641752c5fb6bce2dce3d7e7625d7a46f1d7c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pycrackhash (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pycrackhash across your stack and pipelines.
If you installed it — respond
pycrackhash 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 pycrackhash was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks pycrackhash before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. pycrackhash on PyPI has been identified as a malicious package (versions 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-08-kertash

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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