Which versions of atio-obfuscator are malicious?

The following PyPI versions of atio-obfuscator are flagged malicious: 0.1.4. Treat any of these as compromised.

How do I remediate atio-obfuscator if I installed it?

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

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

Yes — atio-obfuscator is associated with the RLMA-2024-03566, RLUA-2024-07840 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 atio-obfuscator across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for atio-obfuscator (version 0.1.4).

Malicious package

atio-obfuscatorPyPI

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

Malicious code in atio-obfuscator (PyPI)

MAL-2024-4786

Immediate action

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

pip uninstall atio-obfuscator

Malicious versions

1 flagged

0.1.4

Indicators of compromise (SHA-256)

6575976b23cca19538f01fa5759cf6d366f34cf8b7177351ae485b48ce621dae

59912c8e743717b8e3f80db52eed7bce7e629dc9b19bc9783c72c5cd61ee5254

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03566RLUA-2024-07840

Credits

ReversingLabs · finder

Detect & block this

O3 blocks atio-obfuscator-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