Which versions of filename are malicious?

The following PyPI versions of filename are flagged malicious: 0.0.5, 0.0.6, 1.3. Treat any of these as compromised.

How do I remediate filename if I installed it?

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

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

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

Search your lockfiles and build artifacts for filename (3 malicious versions).

Malicious package

filenamePyPI

filename is a confirmed malicious PyPI package (MAL-2024-5141) that executes malicious code on install (malicious versions 0.0.5, 0.0.6, 1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in filename (PyPI)

MAL-2024-5141

Immediate action

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

pip uninstall filename

Malicious versions

3 flagged

0.0.50.0.61.3

Indicators of compromise (SHA-256)

2100fa8018879a58365c26c94179ca43898ff5e3493a4f0115a560452aa06e51

5ef287296c7b5eccab8115dc4ce2b5e8e965f5beebda2930bf1eef575b1957ef

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03921RLUA-2024-08277

Credits

ReversingLabs · finder

Detect & block this

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