Which versions of tls-client-py are malicious?

The following PyPI versions of tls-client-py are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate tls-client-py if I installed it?

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

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

Yes — tls-client-py is associated with the RLMA-2024-04959, RLUA-2024-09432 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 tls-client-py across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tls-client-py (version 1.0).

Malicious package

tls-client-pyPyPI

tls-client-py is a confirmed malicious PyPI package (MAL-2024-6155) 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 tls-client-py (PyPI)

MAL-2024-6155

Immediate action

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

pip uninstall tls-client-py

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

b0066923a8c4316e3656576d53ab12b0dffc6eb94e40d0758b3d96506be5c5d3

0fec1ba04452929ffa8073a75e61ed59e429a430dcb3cf28ed9b891a8729e709

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tls-client-py (version 1.0).
If you installed it — respond
Remove tls-client-py 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 tls-client-py 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. tls-client-py 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-04959RLUA-2024-09432

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks tls-client-py-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