Which versions of telegreph are malicious?

The following PyPI versions of telegreph are flagged malicious: 0.2, 0.3. Treat any of these as compromised.

How do I remediate telegreph if I installed it?

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

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

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

Malicious package

telegrephPyPI

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

MAL-2025-193008

Immediate action

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

pip uninstall telegreph

What this malware does

The package, distinguished as a speed testing or typosquatted Telegram library, contains a Telegram bot to perform remote control of the computer

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

Campaign: 2025-10-speedd-testing-bot

Reasons (based on the campaign):

rat
Downloads and executes a remote malicious script.
typosquatting

Malicious versions

2 flagged

0.20.3

Indicators of compromise (SHA-256)

cca72e5a6a205d657e13d29aee3f5448061afd17f222f11db168ef8a20744992

7d8ae36486ed48aca6b53bb6dbb139cf5c1567dd377f09d48d6fb173ea521126

ca45cc6b3f7fe302114930490eabfda251eb55a13e807e784dbf95c82c2c445c

7c70b41092e7a6fab378c7071947d46e295858b6af5658b3c22dfe4f69c6ff76

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

Campaign

2025-10-speedd-testing-bot

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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