Which versions of textgradient are malicious?

The following PyPI versions of textgradient are flagged malicious: 0.1, 0.2, 0.3. Treat any of these as compromised.

How do I remediate textgradient if I installed it?

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

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

Yes — textgradient is associated with the RLMA-2025-02540, 2025-03-textgradient, RLUA-2026-00815, RLUA-2026-02082 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 textgradient 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 textgradient (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging textgradient across your stack and pipelines.

Malicious package

textgradientPyPI

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

MAL-2025-3473

Immediate action

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

pip uninstall textgradient

What this malware does

Highly obfuscated code that during import downloads a remote script with another obfuscated code. The repository with remote script also contains clearly infostealer code

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-03-textgradient

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote malicious script.

Malicious versions

3 flagged

0.10.20.3

Indicators of compromise (SHA-256)

fd6b3e172a66666d0d57c37dd7ee403d3d21fce16375a04d81bd642a5ec11f79

379db80ee13908937315f272639af6fee599bd03179d246cb41eb981df3d2c90

7fe681cdeb2892cd4e567b4ac8aeb6e0eb22885cce024238e010af54711831ec

8e18e1bb91c50f9e93bff6c9acaa68618e32a7c687d6987a3ef69a8e32843690

43ba0211625dbb892bebc696f492de54ee1135e3e875254b897b713e5ee8f165

30ddb6687b64b39bd8a8a87ed82e16de8a5b38f40795f763e707405b4d05acec

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 textgradient (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging textgradient across your stack and pipelines.
If you installed it — respond
textgradient 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 textgradient 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 textgradient 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. textgradient on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025402025-03-textgradientRLUA-2026-00815RLUA-2026-02082

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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