Which versions of ttat-api-test are malicious?

The following PyPI versions of ttat-api-test are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

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

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

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

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

Malicious package

ttat-api-testPyPI

Malicious code in ttat-api-test (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12367

Immediate action

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

pip uninstall ttat-api-test

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

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

84e21627e718bc7d043fcf4ed50ec712682f95eb4531ea6c06f80fd0c296aa7a

d20a1138316e89f4d0fa408c74d2aadafbb6d6c62a1bfb5fdececb77409aadd4

e9b981e99d90b9d5c30a1d65c02b5dc5f1d40b19145416fb8065a890c593e698

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 ttat-api-test (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ttat-api-test across your stack and pipelines.
If you installed it — respond
ttat-api-test 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-test 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 ttat-api-test 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. ttat-api-test on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0 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-test-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