Which versions of ttat-api are malicious?

The following PyPI versions of ttat-api are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate ttat-api if I installed it?

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

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

Yes — ttat-api is associated with the 2024-08-byted-22.ax 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 ttat-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ttat-api (version 1.0.5).

Part of a larger attack: 2024-08-byted-22.ax published 9 malicious packages. See the full campaign →

Malicious package

ttat-apiPyPI

Advisory published Aug 22, 2024Updated Dec 12, 2025

ttat-api is a confirmed malicious PyPI package (MAL-2024-12366) that steals credentials and exfiltrates sensitive data (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ttat-api (PyPI)

MAL-2024-12366

Immediate action

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

pip uninstall ttat-api

What this malware does

Collects basic information about the system, most probably a pentest or bug bounty.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-08-byted-22.ax

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

6918ae314f1bdf20816d2da5f44532bbabc21ca5f698a6119c9878c20d309504

171a49cab7c7b9f2c358c0e14882706dcd80cde089799698400155ee26240e80

d30358e52cc6bf4156b509a01d73b5977b953cf60bcbb43a219f9d2ba13b40f6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for ttat-api (version 1.0.5).
If you installed it — respond
ttat-api 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 ttat-api 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. ttat-api on PyPI has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-08-byted-22.ax

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks ttat-api-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