Which versions of telebot-infoe are malicious?

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

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

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

If telebot-infoe was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is telebot-infoe part of a known attack campaign?

Yes — telebot-infoe 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-infoe across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for telebot-infoe (version 0.3).

Part of a larger attack: 2025-10-speedd-testing-bot published 26 malicious packages. See the full campaign →

Malicious package

telebot-infoePyPI

Advisory published Feb 18, 2026Updated Jul 20, 2026

telebot-infoe is a confirmed malicious PyPI package (MAL-2026-934) that steals credentials and exfiltrates sensitive data (malicious version 0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in telebot-infoe (PyPI)

MAL-2026-934

Immediate action

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

pip uninstall telebot-infoe

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):

typosquatting
Downloads and executes a remote malicious script.
rat

Malicious versions

1 flagged

0.3

Indicators of compromise (SHA-256)

4dadd8bb17144a1726c97ec0472de592532f72b8c57fdd87ce1364e43241832d

d5e2bec44b62136631295964c1d4571f295ca9cdb6f433246d2500f60bbaafe9

756b42c1ad444b8b2f5572424336c2ab86cb6b98c2545202e84f146c2898224f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for telebot-infoe (version 0.3).
If you installed it — respond
telebot-infoe 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-infoe was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. telebot-infoe on PyPI has been identified as a malicious package (version 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 telebot-infoe-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

Explore

All malware advisories How O3 detects malware Vulnerability database