Which versions of tlsclient-api are malicious?

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

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

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

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

Yes — tlsclient-api is associated with the RLMA-2024-04961, RLUA-2024-09434 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 tlsclient-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tlsclient-api (version 1.0).

Malicious package

tlsclient-apiPyPI

tlsclient-api is a confirmed malicious PyPI package (MAL-2024-6157) that executes malicious code on install (malicious version 1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tlsclient-api (PyPI)

MAL-2024-6157

Immediate action

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

pip uninstall tlsclient-api

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

ce2f9835d2b8b6c0ae240180c88c22d9f35acfbfb759ccbd110045d0faea0011

bc47f7d66928b3e7d4ee00a4c3660716ef576e74296d99dbf3114d0d1c2fc979

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04961RLUA-2024-09434

References

Credits

ReversingLabs · finder

Detect & block this

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