Which versions of unizip are malicious?

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

How do I remediate unizip if I installed it?

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

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

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

Malicious package

unizipPyPI

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

MAL-2025-192689

Immediate action

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

pip uninstall unizip

What this malware does

During initialization of the archive-support class, the package download and executes remote malicious code

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)

36d788bf5be2a646474da2cb929d2b24c328cd5bbd997697780a15da181d1053

9fadf0a794ba575006bbe788d8bbdd833d55dec61470f60bcc310f43c2d99b68

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 unizip (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unizip across your stack and pipelines.
If you installed it — respond
unizip 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 unizip 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 unizip 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. unizip 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 unizip-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