Which versions of tronjoi are malicious?

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

How do I remediate tronjoi if I installed it?

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

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

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

Malicious package

tronjoiPyPI

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

MAL-2025-6607

Immediate action

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

pip uninstall tronjoi

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)

d12562efe04a9bec207aea68dcb9185c922a648e85863541c6c8f538c9aaae6f

d754701acf4d2e052ee3cc28aefb3e5bfa9578937d5cf73163c51623be8b80d6

342de1bcc165de314cdb7ae0e0c63021edebd55ed3601024f66a3ffeb9ab807b

291c3478fb237349b2c676795f88731369c209f9328bc3d85818254d1dca424a

bd739956ed6f36038d6a34f58ab87d2a125f3f6573b1f9a65ecb0c3b0e486f2a

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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