Which versions of lolcrazy are malicious?

The following PyPI versions of lolcrazy are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate lolcrazy if I installed it?

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

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

Yes — lolcrazy is associated with the RLMA-2025-04790, 2025-08-k7eel, RLUA-2026-00477 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 lolcrazy 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 lolcrazy (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lolcrazy across your stack and pipelines.

Malicious package

lolcrazyPyPI

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

MAL-2025-47785

Immediate action

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

pip uninstall lolcrazy

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

fe177a961745b1feb621050eabb173599c0277c68bb13dc9dc3751a91e314e53

1a8f9d73ad18e5dca9664044cae693c869be0d85d6ceb2fb2ac8e39688a195d1

9e3fc2ad284d2b4b286da2fc5762b18aade19bc38871779157c54cdb6ae8b4cd

b6820736af478d2041137707e7a7024e4831c4b47f03895d493ab964c4d5e1c7

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

Campaign

RLMA-2025-047902025-08-k7eelRLUA-2026-00477

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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