Which versions of tronkeyspy are malicious?

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

How do I remediate tronkeyspy if I installed it?

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

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

Yes — tronkeyspy is associated with the RLMA-2025-04818, 2025-04-tronix, RLUA-2026-00853 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 tronkeyspy 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 tronkeyspy (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 tronkeyspy across your stack and pipelines.

Malicious package

tronkeyspyPyPI

Malicious code in tronkeyspy (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47808

Immediate action

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

pip uninstall tronkeyspy

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)

714a5c366e11f361b5a9921e09cc88295b14dc17b591e9ec4bc44a29450d342c

d2d3c6aad5ef7a4a8b24d2c9686d60095ac4573ccfe562cd2fea1f0385054581

762c52ac89d263a12b871d89f8eda658aaa6cc433251fb764ccc55d28e94f1e1

e7dbe7b036eceb06b58dd7ca8da2f954e7c0d6e4bb9650ecf4b921a1db6fb722

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 tronkeyspy (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 tronkeyspy across your stack and pipelines.
If you installed it — respond
tronkeyspy 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 tronkeyspy 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 tronkeyspy 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. tronkeyspy 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-048182025-04-tronixRLUA-2026-00853

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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