Which versions of tronpyapi are malicious?

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

How do I remediate tronpyapi if I installed it?

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

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

Yes — tronpyapi is associated with the RLMA-2025-03709, 2025-04-tronix, RLUA-2026-00861 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 tronpyapi 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 tronpyapi (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 tronpyapi across your stack and pipelines.

Malicious package

tronpyapiPyPI

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

MAL-2025-6610

Immediate action

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

pip uninstall tronpyapi

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)

e52ef18b22f017f613d71d24c456bbef745d9266cdc1ace0d9a82b64e1de7149

75c25a6760803d4b2c36508054fc980be953773be21c0aede396796a9f149fef

3937a7f13d0db04c75985a870ed1eec73aaaff23ce5c45d9fcb64a239576cfc7

aec8f4fc087447285eb8e8def527675f78248b1eaef7e462b42b8b63f8d2e8a8

47d358f66e371fc4aa125297ce517c0e045deea0e5ee750c51ab9b32a1dbcc54

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 tronpyapi (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 tronpyapi across your stack and pipelines.
If you installed it — respond
tronpyapi 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 tronpyapi 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 tronpyapi 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. tronpyapi 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-037092025-04-tronixRLUA-2026-00861

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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