Which versions of crpt are malicious?

The following PyPI versions of crpt are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate crpt if I installed it?

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

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

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

Search your lockfiles and build artifacts for crpt (version 1.0.0).

Malicious package

crptPyPI

Advisory published Jul 12, 2025Updated Dec 12, 2025

crpt is a confirmed malicious PyPI package (MAL-2025-191707) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in crpt (PyPI)

MAL-2025-191707

Immediate action

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

pip uninstall crpt

What this malware does

Importing the module starts downloading or decrypting, and then executing an executable being a wide recognized malware/Infostealer (Redline family)

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

Campaign: 2025-07-crpt

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
Downloads and executes a remote malicious script.
exfiltration-crypto
malware

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a09ea7b39538033fb3fa6f3ec58161047f420c951db35ed069764d502f4a496b

27d11f666afed6152d1e6e4f510ee725397a411a11ca6338fb5583dd21b400cc

413905aa18fd3109b1d65479d6d50a9a3907018131dd7455a77263528f59fb75

Detection & response playbook

Credential / info stealer

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

Campaign

2025-07-crpt

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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