Which versions of tq95 are malicious?

The following PyPI versions of tq95 are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6. Treat any of these as compromised.

How do I remediate tq95 if I installed it?

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

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

Yes — tq95 is associated with the RLMA-2025-03703, 2025-07-tq95, RLUA-2026-00834 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 tq95 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tq95 (6 malicious versions).

Malicious package

tq95PyPI

Advisory published Jul 7, 2025Updated Mar 19, 2026

tq95 is a confirmed malicious PyPI package (MAL-2025-6604) that steals credentials and exfiltrates sensitive data (malicious versions 0.1, 0.2, 0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tq95 (PyPI)

MAL-2025-6604

Immediate action

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

pip uninstall tq95

What this malware does

Importing the module starts an infostealer exfiltrating browser data, passwords, crypto wallets and implants a Discord stealer.

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

Campaign: 2025-07-tq95

Reasons (based on the campaign):

infostealer
exfiltration-browser-data
files-exfiltration
exfiltration-crypto
obfuscation

Malicious versions

6 flagged

0.10.20.30.40.50.6

Indicators of compromise (SHA-256)

ad1a5fbc90cc7cdc728f4ad87541dc860cb04b05f04e31e7790732f81ca14499

df9d5158b350028abdb299c9f5f7145f40f68e3d260c8f3d31012e60ae4ecddc

abb1e0b01bcc48bdbb798a617be723bf433722a7bede307de21214a92d569949

bdb5280485de8470ef36a19819fa297cf1c0dc571f0893592cc4546a43a8c867

bb1e03ccb569a30370a573feccb7f09e5701f7572d5cb98e7d8171464ff42c3e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tq95 (6 malicious versions).
If you installed it — respond
tq95 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 tq95 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. tq95 on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3, 0.4, 0.5, 0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-037032025-07-tq95RLUA-2026-00834

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database