Which versions of tronkeypy are malicious?

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

How do I remediate tronkeypy if I installed it?

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

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

Yes — tronkeypy is associated with the RLMA-2025-04817, 2025-04-tronix, RLUA-2026-00852 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 tronkeypy across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

tronkeypyPyPI

Advisory published Sep 12, 2025Updated Mar 19, 2026

tronkeypy is a confirmed malicious PyPI package (MAL-2025-47807) 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 tronkeypy (PyPI)

MAL-2025-47807

Immediate action

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

pip uninstall tronkeypy

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)

9cfd8f0a4b7dca8e2e35d411949768d04384f507e61bb7f31cc03fd31a1a7c61

312a0ec68af533d425ccdf6a359beca19c6ec31e5306b1a420df4d113177e204

15beba1021e7f60daed074087734c4a931b0b0d93695e6d1bf28aea909f41a80

7a8bf9adb7205ec89e49d3e2eeb767d675f40de38061ca92d5b81a217407f216

Detection & response playbook

Credential / info stealer

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

RLMA-2025-048172025-04-tronixRLUA-2026-00852

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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