Which versions of trongrider are malicious?

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

How do I remediate trongrider if I installed it?

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

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

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

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

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

Malicious package

trongriderPyPI

Advisory published Jul 20, 2026Updated Aug 4, 2026

trongrider is a confirmed malicious PyPI package (MAL-2026-10929) 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 trongrider (PyPI)

MAL-2026-10929

Immediate action

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

pip uninstall trongrider

What this malware does

The package exposes a function perm(private_key) that POSTs the caller-supplied TRON private key as JSON to the hardcoded URL https://reda-sequestered-justine.ngrok-free.dev/tron. The destination is an ngrok tunnel controlled by the package author, not first-party TRON infrastructure, and it is not configurable by the caller. Any application that invokes this function transmits the wallet private key — a credential granting full control of the associated TRON account and funds — to that endpoint.

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)

0d44486dc374cb50abaad84a7086859ce3c2a7e5b17a790aae5b426c4cf2a1e0

0766a0a8222cb9a7a188ad8c88daf73b102036079be073f01661cde1622b99b5

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for trongrider (version 0.0.1).
If you installed it — respond
trongrider 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 trongrider 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. trongrider 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-011092

References

Credits

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

Detect & block this

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