Which versions of trongapy are malicious?

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

How do I remediate trongapy if I installed it?

Remove trongapy from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is trongapy part of a known attack campaign?

Yes — trongapy 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.

Can O3 Security detect trongapy in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking trongapy and packages like it before any post-install script runs.

Malicious package

trongapyPyPI

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

MAL-2026-5683

Immediate action

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

pip uninstall trongapy

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)

aacf2f97461deed6a022e67932b5b4af6e99163664e4de6b0a16256fd68a3cd4

Frequently asked questions

No. trongapy 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) · analyst

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection