Which versions of aiogrem are malicious?

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

How do I remediate aiogrem if I installed it?

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

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

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

Search your lockfiles and build artifacts for aiogrem (version 0.2).

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

Malicious package

aiogremPyPI

Advisory published Dec 31, 2025Updated Jul 20, 2026

aiogrem is a confirmed malicious PyPI package (MAL-2025-193007) that steals credentials and exfiltrates sensitive data (malicious version 0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aiogrem (PyPI)

MAL-2025-193007

Immediate action

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

pip uninstall aiogrem

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)

2429ae6fbbf21c43b0bb5cc9a1ed320a2b7df0433adac380ec5902508727bc98

5bca22666e394214defbab3bb34c17034301aefa5efd9413036e56f803c0a91d

6b7a513d1afdad2735edfc7f4f123ae0e428948ff4c0a16330428060018a896d

93b4e84526de7487a15f394e1677d9304b479d1bdf34d57bf6b8e541642a2505

c840783f6a39e0bcdd9e2ccfab9a8cdec3bde9faf51e94211b6de13a052a8c08

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for aiogrem (version 0.2).
If you installed it — respond
aiogrem 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 aiogrem 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. aiogrem 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 aiogrem-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