Which versions of zyto are malicious?

The following PyPI versions of zyto are flagged malicious: 0.2.0, 0.2.1, 0.2.2, 0.2.3. Treat any of these as compromised.

How do I remediate zyto if I installed it?

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

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

Yes — zyto is associated with the 2026-11-filipt 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 zyto across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zyto (4 malicious versions).

Malicious package

zytoPyPI

Advisory published Nov 3, 2026Updated Nov 3, 2026

zyto is a confirmed malicious PyPI package (MAL-2026-18582) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.0, 0.2.1, 0.2.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zyto (PyPI)

MAL-2026-18582

Immediate action

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

pip uninstall zyto

What this malware does

The package ships an executable started during the building of a wheel/installation. It has been identified as malicious by some AV vendors, but primarily it is a preparation to embed a RAT as in another campaign's package.

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

Campaign: 2026-11-filipt

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
malware
rat

Malicious versions

4 flagged

0.2.00.2.10.2.20.2.3

Indicators of compromise (SHA-256)

817f92245d406e764c42e8038b2ea559a6bd6deb1706b80e2699e0ab724111a2

Detection & response playbook

Credential / info stealer

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

Campaign

2026-11-filipt

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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