Which versions of aaaazzzzaz are malicious?

The following PyPI versions of aaaazzzzaz are flagged malicious: 2.26. Treat any of these as compromised.

How do I remediate aaaazzzzaz if I installed it?

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

If aaaazzzzaz was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is aaaazzzzaz part of a known attack campaign?

Yes — aaaazzzzaz is associated with the 2026-06-easyaillm 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 aaaazzzzaz across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aaaazzzzaz (version 2.26). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aaaazzzzaz across your stack and pipelines.

Malicious package

aaaazzzzazPyPI

Malicious code in aaaazzzzaz (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5874

Immediate action

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

pip uninstall aaaazzzzaz

What this malware does

During installation, the code attempts to download and start a malicious executable.

Likely related to 2025-08-raknet-testing-package.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-06-easyaillm

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware
tool:mshta

Malicious versions

1 flagged

2.26

Indicators of compromise (SHA-256)

2e51c0c88249f30e4c3aa99ad20f2bdbb7177eac729680ca2c7fec13ec9de1eb

c1698c50a4706300296a442bbb0ae57280e870d8c83575d68218143e4ffd6645

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aaaazzzzaz (version 2.26). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aaaazzzzaz across your stack and pipelines.
If you installed it — respond
aaaazzzzaz 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 aaaazzzzaz was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks aaaazzzzaz before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. aaaazzzzaz on PyPI has been identified as a malicious package (version 2.26 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-easyaillm

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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