Which versions of aiohappyeyeball are malicious?

The following PyPI versions of aiohappyeyeball are flagged malicious: 2.6.1. Treat any of these as compromised.

How do I remediate aiohappyeyeball if I installed it?

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

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

Yes — aiohappyeyeball is associated with the RLMA-2025-05583, 2025-10-asynhttp, RLUA-2026-00041 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 aiohappyeyeball 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 aiohappyeyeball (version 2.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aiohappyeyeball across your stack and pipelines.

Malicious package

aiohappyeyeballPyPI

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

MAL-2025-191616

Immediate action

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

pip uninstall aiohappyeyeball

What this malware does

Malicious copy of the legit aiohappyeyeballs package, the pycache/staggerd.pyc contains a suspicious binary content (which seems not to be a valid PYC)

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

Campaign: 2025-10-asynhttp

Reasons (based on the campaign):

typosquatting
exfiltration-generic
obfuscation
clones-real-package
native-extension

Malicious versions

1 flagged

2.6.1

Indicators of compromise (SHA-256)

c2eaa21adf5623d3117f788f57020f42fbec6493a7cd96130f6b5a22afd90976

419e887ea734cca886f42852f3fb9c909c929a28e2b5ac2c0e336d0cabea5624

b39e28cdffb4bcc78f050861bc6c2b3d30b6c71996f87a4759b49e5f77b2d2fe

c4026e5d61b51d8fb2688488995ad95c662a15084e5c4799b0e68d0962291056

4b1f0143fe6c7e24e0b3ddb4783d05395c2049b5e8e5357a45de4e1f04593158

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 aiohappyeyeball (version 2.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aiohappyeyeball across your stack and pipelines.
If you installed it — respond
aiohappyeyeball 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 aiohappyeyeball 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 aiohappyeyeball 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. aiohappyeyeball on PyPI has been identified as a malicious package (version 2.6.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-055832025-10-asynhttpRLUA-2026-00041

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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