Which versions of myownpyfiglet are malicious?

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

How do I remediate myownpyfiglet if I installed it?

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

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

Yes — myownpyfiglet is associated with the RLMA-2025-03016, 2025-05-rich-figlet, RLUA-2026-00548 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 myownpyfiglet 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 myownpyfiglet (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 myownpyfiglet across your stack and pipelines.

Malicious package

myownpyfigletPyPI

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

MAL-2025-5119

Immediate action

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

pip uninstall myownpyfiglet

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

74a7f58af3314983edde6befa7ec2fb6fdab2337d0ac5f293c5156de6fc9da8f

1222a5e7e6a1a7c9d034ec124fdf879e124d4a379cc981f33f2a501af0f7aaba

feb59db3efc9397070b6fcdf08762e0defb77d34e5ababf463e3c1a7a1f5b927

f7ad639a3307a53d4f88f630be9fc82a7b6e3f992d6bc47430a4f33ceef9c981

1d91f1a21066383111eebb537d30059b74a0981314b5753ee5ce064a50c593f6

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 myownpyfiglet (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 myownpyfiglet across your stack and pipelines.
If you installed it — respond
myownpyfiglet 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 myownpyfiglet 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 myownpyfiglet 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. myownpyfiglet 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-030162025-05-rich-figletRLUA-2026-00548

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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