Which versions of yzip are malicious?

The following PyPI versions of yzip are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate yzip if I installed it?

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

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

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

Search your lockfiles and build artifacts for yzip (version 0.1.0).

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

Malicious package

yzipPyPI

Advisory published Dec 11, 2025Updated Feb 26, 2026

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

Malicious code in yzip (PyPI)

MAL-2025-192468

Immediate action

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

pip uninstall yzip

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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

81477965a8a70d1ffef0d388478d3e05ef2eea54ade0a9c00ef923deb41b00cf

e1d6b6d65166893740b44fc5d3d3333a9ad2903074ae7620a9b6a61b1c61bdf6

4c4132881c30775abaca8fc6f2d44ce9382b50e8d62a6b26c3410e03359baefd

Detection & response playbook

Credential / info stealer

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