Which versions of uzip are malicious?

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

How do I remediate uzip if I installed it?

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

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

Yes — uzip 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 uzip 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 uzip (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uzip across your stack and pipelines.

Malicious package

uzipPyPI

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

MAL-2025-191919

Immediate action

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

pip uninstall uzip

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

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

b1d7db00ba4f8c670ae2a1b70169782860303f25f14d7130b4856ce72981f265

ee20087db4a86ce68765ba8046732e8f1fc906c58a0303e836429a63788dc97f

5aaba949ae7faf2413a0b1fbe36653883d7250a9d8fe71e5eca150bc6b2c9665

d7e4a8570ffc3f4656de4dd651ae64ddb7612b68557086b052dda63c88e23908

b674b95755c5b73a12e4acd5bf570d6b333cc7cfb5ddf21b899e5e715718b52b

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 uzip (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uzip across your stack and pipelines.
If you installed it — respond
uzip 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 uzip 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 uzip 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. uzip on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 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 uzip-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