Which versions of libmelee are malicious?

The following PyPI versions of libmelee are flagged malicious: 0.0.0.1. Treat any of these as compromised.

How do I remediate libmelee if I installed it?

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

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

Yes — libmelee is associated with the RLMA-2025-01969 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 libmelee across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for libmelee (version 0.0.0.1).

Malicious package

libmeleePyPI

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

Malicious code in libmelee (PyPI)

MAL-2025-2971

Immediate action

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

pip uninstall libmelee

Malicious versions

1 flagged

0.0.0.1

Indicators of compromise (SHA-256)

2e01a436daf3d9e1397fd1f806af6e3616953ec97cfa8f949a5e622dffeec012

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-01969

Credits

ReversingLabs · finder

Detect & block this

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