Which versions of cittronn are malicious?

The following PyPI versions of cittronn are flagged malicious: 3. Treat any of these as compromised.

How do I remediate cittronn if I installed it?

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

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

Yes — cittronn 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 cittronn across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cittronn (version 3).

Malicious package

cittronnPyPI

Advisory published Jul 26, 2024Updated Jan 14, 2026

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

Malicious code in cittronn (PyPI)

MAL-2024-12236

Immediate action

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

pip uninstall cittronn

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

Indicators of compromise (SHA-256)

859e10aae35c888d78c8dd8ae1d8a9bc8f7e1e5c83608aaededfb3931eec9ddf

dfa8d2dd5fa7ca684cd31b55440d9eb21ff2197a6a774c36b07fe88f804554d6

31dbb318d93b1d1c879be4f71d7ad2c106505248e2ed4cf20a76b750cb39ef99

d2ab856578bf05c48f306e1fdbdcc3b9b6ec817f95939dde804901d9bea94935

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for cittronn (version 3).
If you installed it — respond
cittronn 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 cittronn 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. cittronn on PyPI has been identified as a malicious package (version 3 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 cittronn-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