Which versions of aiogt are malicious?

The following PyPI versions of aiogt are flagged malicious: 1.0.0, 1.0.0.post1, 1.0.0rc1, 1.0.0rc2. Treat any of these as compromised.

How do I remediate aiogt if I installed it?

Remove aiogt from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed aiogt — how do I know if it already compromised me?

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

Yes — aiogt is associated with the RLMA-2024-07802 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 aiogt across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aiogt (4 malicious versions).

Malicious package

aiogtPyPI

aiogt is a confirmed malicious PyPI package (MAL-2024-9936) that executes malicious code on install (malicious versions 1.0.0, 1.0.0.post1, 1.0.0rc1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aiogt (PyPI)

MAL-2024-9936

Immediate action

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

pip uninstall aiogt

Malicious versions

4 flagged

1.0.01.0.0.post11.0.0rc11.0.0rc2

Indicators of compromise (SHA-256)

3e26eddf7622e29dfbb4b554f3b2e2acf17195dc3eccaab157488e0cdbef7394

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for aiogt (4 malicious versions).
If you installed it — respond
Remove aiogt from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If aiogt 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. aiogt on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.0.post1, 1.0.0rc1, 1.0.0rc2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-07802

Credits

ReversingLabs · finder

Detect & block this

O3 blocks aiogt-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database