Which versions of malimaloo are malicious?

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

How do I remediate malimaloo if I installed it?

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

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

Yes — malimaloo is associated with the RLMA-2025-03638, 2025-07-malimalo, RLUA-2026-00490 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 malimaloo 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 malimaloo (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 malimaloo across your stack and pipelines.

Malicious package

malimalooPyPI

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

MAL-2025-6542

Immediate action

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

pip uninstall malimaloo

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)

f410ef7535e010e1e283416e8c5d9f3bb1dc0bf1667b4143674e424167202125

93ab3691b0e53219db1c79882a085b949b0d3cde8d3efc4bb4e0bba86a68fb0b

cfbfc14d4873b047e472e26b760198ecc402eb1ed35d59ab3ace8dc31936690f

4b344f7c45a7199088d9b12b4f990d79b8e38eb2821567bd42a388ad6420d0cd

fe57b8aa147cc1c4152c4cb98db9b6913618c4daa63975f16e030fe281eb8e66

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for malimaloo (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 malimaloo across your stack and pipelines.
If you installed it — respond
Remove malimaloo 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 malimaloo 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 malimaloo 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. malimaloo 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-036382025-07-malimaloRLUA-2026-00490

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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