Which versions of telegrem are malicious?

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

How do I remediate telegrem if I installed it?

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

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

Yes — telegrem 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 telegrem 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 telegrem (version 0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging telegrem across your stack and pipelines.

Malicious package

telegremPyPI

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

MAL-2025-192943

Immediate action

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

pip uninstall telegrem

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

1 flagged

0.2

Indicators of compromise (SHA-256)

8fc678ba7dec176faf115763df24c8c397ecc0ad82cc06f4cc15a1bf35986068

f2186dc29d07dc851d756bae0b5d080ebe5923efe6654fdb4aa9ec55bbba9b6a

2723584fe48faac3611b299028807bf1e449a68121701c63856f3bedb943391a

bcadc97eabf5d4ca45383a9cc8ebc08a249778e44a710e130ca6e557e23179d7

68002ae9c382efaebe1b5d9279faebf5cea9c7176a672244040fc072cb6eee80

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 telegrem (version 0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging telegrem across your stack and pipelines.
If you installed it — respond
telegrem 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 telegrem 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 telegrem 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. telegrem on PyPI has been identified as a malicious package (version 0.2 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 telegrem-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