Which versions of trongridlib are malicious?

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

How do I remediate trongridlib if I installed it?

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

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

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

Malicious package

trongridlibPyPI

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

MAL-2025-5140

Immediate action

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

pip uninstall trongridlib

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)

14a185ae6d395fabdd232329b12c9ffb499d2d6bb94997b05a64dcf0311c85e8

bd7414968f3b760ecf2c2dc1878aa07c133868f5ad8ff82b57f6eeae5defa5aa

810f3d44ffd0654acef07cf5bc57e4c1c8daa207332751a60c14f29f64832560

ca892ad85e7fd2c20a831766c21b07abeddabbca06953b3fb599641c43a4ed32

d0550d89034fc0a911f0380b6973ae9d249602e38e33f332cee340876e88b73b

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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