Which versions of zamino are malicious?

The following PyPI versions of zamino are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate zamino if I installed it?

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

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

Yes — zamino is associated with the 2025-06-sorex 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 zamino across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zamino (2 malicious versions).

Malicious package

zaminoPyPI

Advisory published Jun 14, 2025Updated Dec 12, 2025

zamino is a confirmed malicious PyPI package (MAL-2025-191942) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zamino (PyPI)

MAL-2025-191942

Immediate action

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

pip uninstall zamino

What this malware does

Clones of libraries to access Aminoapps (e.g. legitimate package amino.fix) with added exfiltration of the given credentials

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-06-sorex

Reasons (based on the campaign):

exfiltration-credentials
action-hidden-in-lib-usage
clones-real-package

Malicious versions

2 flagged

1.0.01.1.0

Indicators of compromise (SHA-256)

087098aa6e5900b723dcf37b2b0cf7158ecfd55c3cbce2232dac1ef83b6e5440

c9ada91851d5e9411f5c74d5ea595be092fc2e4d2e8f7f7c995b6fbb6bd90d00

f6c0a1f1d6133c6d76f2e70fd50861a958bd9bae8936b0b2f59950c32f8b3949

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for zamino (2 malicious versions).
If you installed it — respond
zamino 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 zamino 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. zamino on PyPI has been identified as a malicious package (versions 1.0.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-06-sorex

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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