Which versions of tronix are malicious?

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

How do I remediate tronix if I installed it?

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

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

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

Malicious package

tronixPyPI

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

MAL-2025-4244

Immediate action

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

pip uninstall tronix

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)

117ba33d3377ab55244863ed8a0059cf7ea909419bc059082a0c41494c156f5e

cced3d1cdb765e10f8137d9f937a29853c0899c3fbd9654b3ba4c9190dfd9ad2

439d817a91f26be5494fd1a2621e8dfb3d178167c802bb0ad7bfcf0fa6b9a0d3

2128889899df4a7e046f3f6a886cf9a6ef63caace934e395a34ec93684ccc091

aa42255f6a27d60efaee7b17f9cfb07b9767b3171db6f763f2c0f0d4a5fa4654

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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