Which versions of telebot-bot are malicious?

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

How do I remediate telebot-bot if I installed it?

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

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

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

Malicious package

telebot-botPyPI

Malicious code in telebot-bot (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-192942

Immediate action

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

pip uninstall telebot-bot

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)

5db22f2fdd9938895f4740932ec2a87b0adc7bb61a1196ef793c2bc800e41846

ae13454f920b5cce1011546e4802ed263ce8218d4b484ef8471142abb42c3f3e

38928e8303576f2c9d38b464dc25b9e45b9e00f863b840852ed3a50afba1f87f

2c72091a2c991d35978758b8587a408a4353ebb5fa596e0391b62b8020e7986b

713a9292b14f503f20aff2bd8b8f13d460d445b6594a4c0f5cb9eb8710b89a54

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 telebot-bot (version 0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging telebot-bot across your stack and pipelines.
If you installed it — respond
telebot-bot 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 telebot-bot 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 telebot-bot 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. telebot-bot 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) · analyst

Detect & block this

O3 blocks telebot-bot-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