Which versions of tlsclient3 are malicious?

The following PyPI versions of tlsclient3 are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate tlsclient3 if I installed it?

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

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

Yes — tlsclient3 is associated with the RLMA-2025-02007, 2025-03-tlsclient3, RLUA-2026-00828 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 tlsclient3 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 tlsclient3 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tlsclient3 across your stack and pipelines.

Malicious package

tlsclient3PyPI

Malicious code in tlsclient3 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3008

Immediate action

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

pip uninstall tlsclient3

What this malware does

Obfuscated code starts a multi-stage infection

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

Campaign: 2025-03-tlsclient3

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

114da211bb86bb267b90de07629442507b6dc330a5a4104e6b1d50510382c9f6

6b18b3332078d66ca6c5318aae4fb7722fd4612a618359566ed01adcf351ee6a

612e1a598a61304a9ae3550acb835ef5962f596bb74e857c2a035ba090e57dc4

115ca597f26fa503ca5ed7936f3efd9f0b2168367d0bf4963877908c996673c5

f479ef03995f033fd9f9ad2ecd6483b3dfdd65113541734c42b4c5e3e42e7250

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

Campaign

RLMA-2025-020072025-03-tlsclient3RLUA-2026-00828

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks tlsclient3-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