Which versions of gtts-lts are malicious?

The following PyPI versions of gtts-lts are flagged malicious: 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 2.5.6, 2.5.7, 2.5.8. Treat any of these as compromised.

How do I remediate gtts-lts if I installed it?

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

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

Yes — gtts-lts is associated with the 2025-09-gtts-lts 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 gtts-lts 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 gtts-lts (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gtts-lts across your stack and pipelines.

Malicious package

gtts-ltsPyPI

Malicious code in gtts-lts (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191745

Immediate action

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

pip uninstall gtts-lts

What this malware does

During the execution, the package silently download and runs a JAR not related to the package job. At the time of analysis, the content was corrupted

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-09-gtts-lts

Reasons (based on the campaign):

Downloads and executes a remote executable.
action-hidden-in-lib-usage

Malicious versions

8 flagged

2.5.12.5.22.5.32.5.42.5.52.5.62.5.72.5.8

Indicators of compromise (SHA-256)

9b0e8dd9fd7e7fccd68fdb4c20f8b89e3d563e48aff667fc0e8080c77b38d4dc

7cfb789704a149f7b741d0c68fcb8a32a1e189444ca36f97e435e59d04e073b8

9c5cebf95ec5752e6643b2129bca380d43d5b1845ae0e5313953749ab3c7c782

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 gtts-lts (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gtts-lts across your stack and pipelines.
If you installed it — respond
gtts-lts 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 gtts-lts 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 gtts-lts 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. gtts-lts on PyPI has been identified as a malicious package (versions 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 2.5.6, 2.5.7, 2.5.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-09-gtts-lts

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks gtts-lts-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