Which versions of trxtwo are malicious?

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

How do I remediate trxtwo if I installed it?

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

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

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

Malicious package

trxtwoPyPI

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

MAL-2025-4249

Immediate action

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

pip uninstall trxtwo

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)

f94ee9234153cbc5857182990a67b9b32fe9ab4ee46bef706a2a8abe570172b3

0cda49b43ab26b9d3abda3cd321d5030b88ce2c1c7eecb1d9777f46a2dcace4f

09ce47da0f3bcc2487cbee6b36384d2712ca257abba3155fcd0f13d9f7acd581

8bfdf7f589b8591574f37d4d1815fc8ce0e67016686b8362bd2f83df25873c92

574ac3ca809856f8b5bc426bc04fe34a07808799e418fedec7e69a0691d28b5a

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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