What does the telethon-pro-safe malware do?

During installation, package executes obfuscated code that starts a RAT-like software allowing remote control and exfiltrating sensitive data. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2026-05-telethon-pro-safe Reasons (based on the campaign): - rat - The package overrides the install command in setup.py to execute malicious code during installation. - exfiltration-credentials - exfiltration-browser-data - The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine. - The package contains code to detect if it is running in a sandbox environment. - The package contains co

Which versions of telethon-pro-safe are malicious?

The following PyPI versions of telethon-pro-safe are flagged malicious: 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4. Treat any of these as compromised.

How do I remediate telethon-pro-safe if I installed it?

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

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

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

Malicious package

telethon-pro-safePyPI

Malicious code in telethon-pro-safe (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4859

Immediate action

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

pip uninstall telethon-pro-safe

What this malware does

During installation, package executes obfuscated code that starts a RAT-like software allowing remote control and exfiltrating sensitive data.

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

Campaign: 2026-05-telethon-pro-safe

Reasons (based on the campaign):

rat
The package overrides the install command in setup.py to execute malicious code during installation.
exfiltration-credentials
exfiltration-browser-data
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
The package contains code to detect if it is running in a sandbox environment.
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
infostealer
obfuscation

Malicious versions

5 flagged

3.0.03.0.13.0.23.0.33.0.4

Indicators of compromise (SHA-256)

8bc2e515c2eb7bf73ea5d532cfb6701dcaf3dd95e9d8248ee3d426b1d0c1ed8c

547838db16ca725408f22270caf4e4e1517d67c7b362784921367678ead4bd51

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

Campaign

2026-05-telethon-pro-safe

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks telethon-pro-safe-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