Which versions of sclite are malicious?

The following PyPI versions of sclite are flagged malicious: 1. Treat any of these as compromised.

How do I remediate sclite if I installed it?

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

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

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

Search your lockfiles and build artifacts for sclite (version 1).

Malicious package

sclitePyPI

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

Malicious code in sclite (PyPI)

MAL-2024-5969

Immediate action

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

pip uninstall sclite

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

ac86a5b40737948a6a6fb5650e16fa861572f80e1fa04e9a77033152064e2d91

391fd08737c078d974acd516c736cad653a896fb8cd9040e27a4f5918cbed640

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04770RLUA-2024-09234

References

blog.virustotal.com

Credits

ReversingLabs · finder

Detect & block this

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