Which versions of azerty123 are malicious?

The following PyPI versions of azerty123 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate azerty123 if I installed it?

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

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

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

Search your lockfiles and build artifacts for azerty123 (version 0.0.1).

Malicious package

azerty123PyPI

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

Malicious code in azerty123 (PyPI)

MAL-2024-4789

Immediate action

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

pip uninstall azerty123

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

18b8f76555078995244d717e58e322f8ce59ca2a918354ccc34f32875fcd672b

545fc33d70fefad9a23f900666cce6c9ce099b36fe75fb5276fcbc97b328096b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03569RLUA-2024-07847

Credits

ReversingLabs · finder

Detect & block this

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