Which versions of rich-figlet are malicious?

The following PyPI versions of rich-figlet are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate rich-figlet if I installed it?

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

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

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

Malicious package

rich-figletPyPI

Malicious code in rich-figlet (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-5130

Immediate action

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

pip uninstall rich-figlet

What this malware does

Malicious clone of pyfiglet. Importing the package starts a series of downloading and executing of obfuscated malicious scripts, partially identified by AVs.

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

Campaign: 2025-05-rich-figlet

Reasons (based on the campaign):

backdoor
clones-real-package
obfuscation
Downloads and executes a remote malicious script.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

1fb8756d54415e4db8b88e0020d0e3790706d1a99fd9e1d35a53c60df6e88bb5

ae8f9120c124773c46c7642ae7b481a2c7fcbb3efc7ede6d3bbd4ae9cd685abb

b97458c87c8580a9cb2f2edc0af2ae40a36489dafa860102eee0307256cb416b

b04142554fcdf43b5220b5775730a7d3ed985e64437f34bbc6217d0753b75d7e

25c5d33ac4481cbfe7f6d5f2efc5bb88a41fbcd5ba7d05e747061aa5f73f3a2a

f2f26985d65eda7a5a25fee5dc18e753eab648063d1d095954b6dd79be7a69d6

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

Campaign

RLMA-2025-030272025-05-rich-figletRLUA-2026-00722

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks rich-figlet-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