Which versions of tronlibpy are malicious?

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

How do I remediate tronlibpy if I installed it?

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

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

Yes — tronlibpy is associated with the RLMA-2025-02604, 2025-04-tronix, RLUA-2026-00858 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 tronlibpy across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

tronlibpyPyPI

Advisory published Apr 28, 2025Updated Mar 19, 2026

tronlibpy is a confirmed malicious PyPI package (MAL-2025-4246) 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 tronlibpy (PyPI)

MAL-2025-4246

Immediate action

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

pip uninstall tronlibpy

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)

2bcc57dc4392869be5d2855295fe0a4c6618d8c2ce99121f1fde1b5d15456302

954a4ebbde79dbdd3915338b3bfae05d7c9daf86bae36020cfb8f71ca235d735

3830f2a3daeaf5ef1da928f6700860805f4fb3b0f955ab814f4742b334ca7868

d6be47219b23557b47b89086eddf06021f43e6be6f0fcbef55b46c31c8a61837

490d422cad746342afcc02b5600f42d9817453a7ce8986d400ebce3b3b2f8c54

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tronlibpy (version 0.0.1).
If you installed it — respond
tronlibpy 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 tronlibpy 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. tronlibpy 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

RLMA-2025-026042025-04-tronixRLUA-2026-00858

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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