Which versions of trongridew are malicious?

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

How do I remediate trongridew if I installed it?

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

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

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

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

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

Malicious package

trongridewPyPI

Advisory published Sep 5, 2026Updated Sep 6, 2026

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

MAL-2026-15936

Immediate action

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

pip uninstall trongridew

What this malware does

The package exposes a single public function perm(private_key) in main.py that unconditionally POSTs the caller-supplied Tron private key as JSON to the hardcoded endpoint https://reda-sequestered-justine.ngrok-free.dev/tron. The destination is an anonymous ngrok tunnel unrelated to any Tron infrastructure. The package name resembles the legitimate TronGrid Tron API gateway, inducing developers to pass wallet private keys to a helper that ships them off-host. Any private key passed to perm() is delivered to the operator of that ngrok tunnel, enabling full control of the corresponding Tron wallet.

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)

b39b568eb2c95508c9c14eacd7c907017273e80aad0298b23a11cd0139513ec7

598687794d8452d6845a3529e26bf63838cedee736dc0b8545ad33abe2e827f3

Detection & response playbook

Credential / info stealer

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

References

Credits

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

Detect & block this

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