Which versions of malimalooo are malicious?

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

How do I remediate malimalooo if I installed it?

Remove malimalooo from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed malimalooo — how do I know if it already compromised me?

If malimalooo was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is malimalooo part of a known attack campaign?

Yes — malimalooo is associated with the RLMA-2025-03639, 2025-07-malimalo, RLUA-2026-00491 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 malimalooo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for malimalooo (version 0.0.1).

Malicious package

malimaloooPyPI

Advisory published Jul 4, 2025Updated Mar 19, 2026

malimalooo is a confirmed malicious PyPI package (MAL-2025-6543) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in malimalooo (PyPI)

MAL-2025-6543

Immediate action

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

pip uninstall malimalooo

What this malware does

The only goal of the package is to execute a webhook or a suspicious file during installation.

Closely related to 2025-07-0x9xnx - created after previous packages were quarantined, similar names, similar usage, but no clearly malicious parts.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-07-malimalo

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d9405b52fce4776f152f3aa76174829a81b8010f8efbd95fd443ef3502d83aa0

0086b1c945f925abb4841ddaac355a2bef7dde3299b695868dd0b138dba890a9

68fa420b0a99cf34a9226a9deb8781219fd54964c91f41a41d2867063a365c32

85338861b17e51d72ce0d2cb7c05b980d4a80038d202626266d9d959bde94f39

073870648c5addedef27c775d4122175d743660d0b32cc6de96af943c74f221c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for malimalooo (version 0.0.1).
If you installed it — respond
Remove malimalooo from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If malimalooo was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. malimalooo 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-036392025-07-malimaloRLUA-2026-00491

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks malimalooo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database