Which versions of mallody are malicious?

The following PyPI versions of mallody are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate mallody if I installed it?

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

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

Yes — mallody is associated with the RLMA-2024-04127, RLUA-2024-08491 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 mallody across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mallody (version 1.0).

Malicious package

mallodyPyPI

mallody is a confirmed malicious PyPI package (MAL-2024-5345) that executes malicious code on install (malicious version 1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mallody (PyPI)

MAL-2024-5345

Immediate action

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

pip uninstall mallody

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

54b3daa048c6ba88a947f0228962f68517fb8d5cc8ea3779f49ae351f32defe5

2b4ddb9832c6553513a6ac7c3ea05fd72d84c2cc1ed23e58791e836cf54ffb02

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for mallody (version 1.0).
If you installed it — respond
Remove mallody 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 mallody 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. mallody on PyPI has been identified as a malicious package (version 1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04127RLUA-2024-08491

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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