Which versions of ziphash are malicious?

The following PyPI versions of ziphash are flagged malicious: 0.1.5, 0.1.6. Treat any of these as compromised.

How do I remediate ziphash if I installed it?

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

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

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

Malicious package

ziphashPyPI

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

MAL-2026-6

Immediate action

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

pip uninstall ziphash

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.50.1.6

Indicators of compromise (SHA-256)

e9a36a54bad10e0f086740a84fd0a837dd4bf1cc9c3c0707648af4bb3855a03e

de06ccd70fe8b69002b46d408c03d54b67573964d444478357e6a7226b418abf

21f7874e4477f3097058af5714eb0bfa79c452d931fa4fd918faf11b1e10e5a8

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

Detect & block this

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