Which versions of a1rn are malicious?

The following PyPI versions of a1rn are flagged malicious: 0.1.0, 0.1.2, 0.1.4. Treat any of these as compromised.

How do I remediate a1rn if I installed it?

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

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

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

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

Malicious package

a1rnPyPI

a1rn is a confirmed malicious PyPI package (MAL-2024-4729) that executes malicious code on install (malicious versions 0.1.0, 0.1.2, 0.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in a1rn (PyPI)

MAL-2024-4729

Immediate action

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

pip uninstall a1rn

Malicious versions

3 flagged

0.1.00.1.20.1.4

Indicators of compromise (SHA-256)

ef4e0243168d0c81602470821287e7369e4c0a21b40e41d999057ce523cc2892

86986b1c2b3c505fa49f7855be3619516e86640bb20457cef06b521823fc342a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03509RLUA-2024-07773

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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