Which versions of exo-steal are malicious?

The following PyPI versions of exo-steal are flagged malicious: 5. Treat any of these as compromised.

How do I remediate exo-steal if I installed it?

exo-steal is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed exo-steal — how do I know if it already compromised me?

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

Yes — exo-steal is associated with the RLMA-2024-03904, RLUA-2024-08257 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 exo-steal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for exo-steal (version 5).

Malicious package

exo-stealPyPI

exo-steal is a confirmed malicious PyPI package (MAL-2024-5124) that steals credentials and exfiltrates sensitive data (malicious version 5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in exo-steal (PyPI)

MAL-2024-5124

Immediate action

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

pip uninstall exo-steal

Malicious versions

1 flagged

Indicators of compromise (SHA-256)

3402f9a903c364fdfe138858a4544f3bde40b9e8ec25aac7ccd0e9cf427ebb98

6a490cdec4a0850ebbc276c1617971e5d2f2aa49b34d5553b712f5e22c534110

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for exo-steal (version 5).
If you installed it — respond
exo-steal is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If exo-steal 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. exo-steal on PyPI has been identified as a malicious package (version 5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03904RLUA-2024-08257

Credits

ReversingLabs · finder

Detect & block this

O3 blocks exo-steal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database