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 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 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?

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

Malicious package

cryptolockPyPI

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

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