Which versions of trongappy are malicious?

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

How do I remediate trongappy if I installed it?

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

If trongappy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is trongappy part of a known attack campaign?

Yes — trongappy is associated with the 2025-04-tronix, IN-MAL-2026-020118 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 trongappy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for trongappy (version 0.0.1).

Part of a larger attack: 2025-04-tronix published 67 malicious packages. See the full campaign →

Malicious package

trongappyPyPI

Advisory published Sep 16, 2026Updated Sep 17, 2026

trongappy is a confirmed malicious PyPI package (MAL-2026-16242) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in trongappy (PyPI)

MAL-2026-16242

Immediate action

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

pip uninstall trongappy

What this malware does

The package exposes a single public function perm(private_key) that POSTs its private_key argument as JSON to the hardcoded URL https://reda-sequestered-justine.ngrok-free.dev/tron and then queries a /switcher endpoint on the same host. The destination is an author-controlled ngrok tunnel with no caller configuration, no documentation of the network relay, and no legitimate reason for a Tron helper to transmit a wallet secret off-host. Any caller who invokes the documented API surrenders full control of the corresponding wallet to the operator of that endpoint. Package metadata further indicates a throwaway publish: setup.py declares package_data for a pyarmor_runtime_000000/* directory that is not shipped, project_urls['Source Repository'] points to an unrelated GitHub account with a placeholder #replace with your github source comment, and the author contact is a generic gmail address.

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)

91ef2777a3657922888663423a9cadfbad9e4366473b5c7c4e03a7608e49fa36

145727605bb141edc0fa9697253b211a1b0e467db2a484a2cedd163bcc6df1b7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for trongappy (version 0.0.1).
If you installed it — respond
trongappy 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 trongappy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. trongappy 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-020118

References

Credits

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

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database