Which versions of cryptolock are malicious?

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

How do I remediate cryptolock if I installed it?

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

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

Yes — cryptolock is associated with the 2026-05-cryptolock 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 cryptolock across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for cryptolock (2 malicious versions).

Malicious package

cryptolockPyPI

Advisory published May 30, 2026Updated May 31, 2026

cryptolock is a confirmed malicious PyPI package (MAL-2026-5089) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cryptolock (PyPI)

MAL-2026-5089

Immediate action

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

pip uninstall cryptolock

What this malware does

During installation, the code tamper with security settings and downloads and executes malicious executable.

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

Campaign: 2026-05-cryptolock

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote executable.
malware

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

b0140fddafadce54debaca7d9591e2770acd987aaf90ec7008b4ae4cf301c233

c492d42ad83f4dccdaa1f373e7ee51c3696684b6f37df5eb90948dccadf52542

Detection & response playbook

Credential / info stealer

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

Campaign

2026-05-cryptolock

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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