Which versions of tronlibapi are malicious?

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

How do I remediate tronlibapi if I installed it?

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

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

Yes — tronlibapi is associated with the RLMA-2025-03707, 2025-04-tronix, RLUA-2026-00857 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 tronlibapi 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 tronlibapi (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tronlibapi across your stack and pipelines.

Malicious package

tronlibapiPyPI

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

MAL-2025-6608

Immediate action

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

pip uninstall tronlibapi

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)

4c1535ed679ae10e582c041dd8190ea54a2a0331c7bc6bc0e288399603d069c2

fb8e88428cacc6722f3df3e0423952927606b3b9c63117a92d85c05194fe1ede

9691194771bc292f5583fcde670bceb7173ec8ec2e1f4a16f1af1322fce21a80

35e00f451cbc17b5dfc4a2eef712deb46cfd05aa6a3c864228eb0bc6a6ffac8f

65d8242949577dac835537fea2a457d570b67a36d3701a70b8fdbcbfcc34bb9f

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 tronlibapi (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tronlibapi across your stack and pipelines.
If you installed it — respond
tronlibapi 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 tronlibapi 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 tronlibapi 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. tronlibapi 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-037072025-04-tronixRLUA-2026-00857

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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