Which versions of gxzip are malicious?

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

How do I remediate gxzip if I installed it?

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

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

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

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

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

Malicious package

gxzipPyPI

Advisory published Dec 10, 2025Updated Feb 26, 2026

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

MAL-2025-192467

Immediate action

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

pip uninstall gxzip

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)

8e0dd8700d5267b8d9bbe270798b11d2250761decf1de89249eab6d90a29080c

5902846f55636040def4b0a9ce433e73d8e2fb554e72ef0755be565b48bb8e82

83b2de6e0a00128511adddefd2ce27fb120acb89299737126e8431d78ccdbafc

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for gxzip (version 0.1.0).
If you installed it — respond
gxzip 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 gxzip 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. gxzip 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 gxzip-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