Which versions of cryptozip are malicious?

The following PyPI versions of cryptozip are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate cryptozip if I installed it?

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

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

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

Search your lockfiles and build artifacts for cryptozip (5 malicious versions).

Part of a larger attack: 2025-11-uzip published 11 malicious packages. See the full campaign →

Malicious package

cryptozipPyPI

Advisory published Dec 28, 2025Updated Feb 26, 2026

cryptozip is a confirmed malicious PyPI package (MAL-2025-192956) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cryptozip (PyPI)

MAL-2025-192956

Immediate action

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

pip uninstall cryptozip

What this malware does

During initialization of the archive-support class, the package starts code from another file and downloads multi-stage malware

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

Campaign: 2025-11-uzip

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware

Malicious versions

5 flagged

0.1.00.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

157ea6b1f1c3d4ed5564c494db770e9156f3e269f12cefec6e4270085a762f26

93ed9c65b2d6e5a305cf48b2028807daca4705f2e5da039d743ff6a2a774fb33

78fb389eebd3298e7c2a90e54342c6e1d321a83c85c297f01b78c8d34ced1185

dbd27f2b5564393737f0c0e22a308a6215b05ee5cc9060fe4695726efa8ae8ea

7a913c42577c1aac9993c7b98f5da58e0045b002d9c7c6d5a8a5c65069297cb9

1dbddd2e65a8e772bc476861ebaa45b3f105f6a42d5f45dde643905aef6020c4

Detection & response playbook

Credential / info stealer

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

Campaign

2025-11-uzip

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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