Which versions of aiohttp-openssl are malicious?

The following PyPI versions of aiohttp-openssl are flagged malicious: 3.13.1. Treat any of these as compromised.

How do I remediate aiohttp-openssl if I installed it?

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

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

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

Malicious package

aiohttp-opensslPyPI

Malicious code in aiohttp-openssl (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191617

Immediate action

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

pip uninstall aiohttp-openssl

What this malware does

Packages silently decrypt content hidden in a dependency and load them as Python extension modules.

In the first wave, those are copies of legitimate aiohttp and aiohappyeyeballs packages. In the second wave, malicious packages created good-looking forks of legitimate rich and pigments packages.

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

3.13.1

Indicators of compromise (SHA-256)

35d37db96c51b64ae5d8de5ae993f0f59b34cd5ccdde92a279efff2e85cd8a55

92f57455ebf461496d8be2499befaa79fe9c3a837220453d86a83e066deed343

c043876b5e096c7a7871643bcb7f9a6c41f5b561e57792478e86fe68eb7452ce

67b219a81e6b2dd7db78b4b223da914ee7baefd0ab056940d3af0bc3b47846a0

694360ba724d11336471a4a39de2f3bc4e2c7870492b44d48c14fcb8a08b0a8f

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

Campaign

RLMA-2025-055842025-10-asynhttpRLUA-2026-00043

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks aiohttp-openssl-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