Which versions of tronapipy are malicious?

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

How do I remediate tronapipy if I installed it?

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

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

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

Malicious package

tronapipyPyPI

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

MAL-2025-6606

Immediate action

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

pip uninstall tronapipy

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)

fa081dbc288e7484e0e0425b26ae874faab190a8bf1ed163d0cb6e4de0f18fb2

c78fe33c5b694a492a295abdfc5224c6977a846cf5ec1e8f1265dafab0758ea8

f708be2fc70e3c2c9dc79ee1706944cb73f9604b496c4171a5971f5c6e0091fe

62107d205608f1909664d5bd1804f61f96c42faf7199a3e208f46de2c6fdadba

8928b5e3b147f92d29ce0e802a448cb955626faa2fc5ec5d3e6adae4cdbdc5ff

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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