Which versions of crunchie are malicious?

The following PyPI versions of crunchie are flagged malicious: 205.0.0. Treat any of these as compromised.

How do I remediate crunchie if I installed it?

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

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

Yes — crunchie is associated with the GENERIC-standard-pypi-install-pentest 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 crunchie across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for crunchie (version 205.0.0).

Malicious package

crunchiePyPI

Advisory published Jul 26, 2024Updated Dec 12, 2025

crunchie is a confirmed malicious PyPI package (MAL-2024-12250) that steals credentials and exfiltrates sensitive data (malicious version 205.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in crunchie (PyPI)

MAL-2024-12250

Immediate action

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

pip uninstall crunchie

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

205.0.0

Indicators of compromise (SHA-256)

e2f69d299e63a1f2c4488b3ec48588c47d0aa74fc50ca582d17b6ea18427faf8

f26d858f791d6d12aab4d70b3f5494c2b675934ba0b13cffa405ecd0686cfa91

3aa6ed6789228cf056ae4169190dd17d2a09a1bfea9e842e49b6a0155ccd80d1

Detection & response playbook

Credential / info stealer

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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