Which versions of uuzip are malicious?

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

How do I remediate uuzip if I installed it?

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

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

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

Search your lockfiles and build artifacts for uuzip (4 malicious versions).

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

Malicious package

uuzipPyPI

Advisory published Nov 22, 2025Updated Feb 26, 2026

uuzip is a confirmed malicious PyPI package (MAL-2025-191918) 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 uuzip (PyPI)

MAL-2025-191918

Immediate action

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

pip uninstall uuzip

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

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

58b899ba2dae09a8971bab3da564442bf25fa773e21eca27cc0989622e9ed7df

bbfdf99ece618455cadb15bcd6d0d6a93707bd72278a58834e74eb88094279ee

9938d9dab0c23fd170a400e54fe14f646dfc7413c53d3e0839ef3992935a988b

cbab6b2a3fbfe9e0d9cef107688b9963ba7c9e6f5f5524dcf07d4bc386ddf1b8

5c70c14f993e25906f5212aa550ae8d703ed0941e517af2b084778d24238557c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for uuzip (4 malicious versions).
If you installed it — respond
uuzip 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 uuzip 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. uuzip on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3 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)

Detect & block this

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