Which versions of tronlab are malicious?

The following PyPI versions of tronlab are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate tronlab if I installed it?

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

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

Yes — tronlab is associated with the 2025-04-tronix 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 tronlab across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tronlab (version 0.0.1).

Part of a larger attack: 2025-04-tronix published 67 malicious packages. See the full campaign →

Malicious package

tronlabPyPI

Advisory published Jun 3, 2026Updated Jun 3, 2026

tronlab is a confirmed malicious PyPI package (MAL-2026-5178) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tronlab (PyPI)

MAL-2026-5178

Immediate action

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

pip uninstall tronlab

What this malware does

Package appears to be designed for private key exfiltration, but no known usage. The name appears to be related to the cryptocurrency TRX (Tron / Tronix). Some packages additionally clone the readme of other, legit libraries. The similar packages are repeating uploaded to PyPI

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

Campaign: 2025-04-tronix

Reasons (based on the campaign):

exfiltration-generic
crypto-related

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

44a6e385a64a2319d00a77e4eb063dd97f8a54dff9df20653fec1f3c3d40ecb9

Detection & response playbook

Credential / info stealer

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

Campaign

2025-04-tronix

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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