Which versions of tronkeeppy are malicious?

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

How do I remediate tronkeeppy if I installed it?

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

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

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

Malicious package

tronkeeppyPyPI

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

MAL-2025-48906

Immediate action

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

pip uninstall tronkeeppy

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)

cd556f64624adc116a1f441d432dff1b8ade30b382fd9d196463d8bb6e87b4ac

91a1e352ed8eef9ed0298bc8b41991d075c5181efb9e0e5888c1531b16adc5bc

415a91c7ce521e9bd46c6e7343acc641436614a73a056c5663496697e4399825

853c9d6e28e3a74950af4c97bd9ebb674104464fe6f8e9cf13430f3b9181bbd6

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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