Which versions of pytzv are malicious?

The following PyPI versions of pytzv are flagged malicious: 0.1.0, 0.2.0, 0.3.0, 0.4.0. Treat any of these as compromised.

How do I remediate pytzv if I installed it?

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

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

Yes — pytzv is associated with the 2025-04-qtpv 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 pytzv 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 pytzv (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pytzv across your stack and pipelines.

Malicious package

pytzvPyPI

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

MAL-2025-191847

Immediate action

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

pip uninstall pytzv

What this malware does

Importing the module starts exfiltration of ".session" files, which appear to be used at least by one Telegram library (https://docs.telethon.dev/en/stable/concepts/sessions.html#what-are-sessions) to store credentials

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

Campaign: 2025-04-qtpv

Reasons (based on the campaign):

files-exfiltration
target:telegram

Malicious versions

4 flagged

0.1.00.2.00.3.00.4.0

Indicators of compromise (SHA-256)

a09605c70fc554bf6db8ef1e12c7138cf9c4f22d69aad1ac9d4ee3bd3e2256f1

bc7b0a2cddf6ee0cc4d688f4136758e0d7aaa99707aa5dd82505d84631d77720

bd273a905ee98fba13687445bc779f84d0def3a34ca038f604a0918411b82fe8

84bc9d390bea11a9eb19e17ef172857b48cd1ae77f8901fbf49083bf7f627487

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 pytzv (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pytzv across your stack and pipelines.
If you installed it — respond
pytzv 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 pytzv 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 pytzv 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. pytzv on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0, 0.3.0, 0.4.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-04-qtpv

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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