Which versions of some-malicious-package are malicious?

The following PyPI versions of some-malicious-package are flagged malicious: 2022.12.7. Treat any of these as compromised.

How do I remediate some-malicious-package if I installed it?

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

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

Yes — some-malicious-package is associated with the RLMA-2024-04825, RLUA-2024-09292 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 some-malicious-package across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for some-malicious-package (version 2022.12.7).

Malicious package

some-malicious-packagePyPI

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

Malicious code in some-malicious-package (PyPI)

MAL-2024-6023

Immediate action

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

pip uninstall some-malicious-package

Malicious versions

1 flagged

2022.12.7

Indicators of compromise (SHA-256)

d44be99266f6d257e3a8c860ce54f889762ce445c6b4814175d17cfb913dfffe

210b05ead476ee4c5bad48f55e4f10b8a67ebea999fceeacdd2efca7ba3390f8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04825RLUA-2024-09292

Credits

ReversingLabs · finder

Detect & block this

O3 blocks some-malicious-package-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