Which versions of aiohttp-ssl are malicious?

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

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

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

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

Yes — aiohttp-ssl is associated with the RLMA-2025-05585, 2025-10-asynhttp, RLUA-2026-00044 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-ssl 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-ssl (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-ssl across your stack and pipelines.

Malicious package

aiohttp-sslPyPI

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

MAL-2025-191618

Immediate action

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

pip uninstall aiohttp-ssl

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)

b61677d7a34093d0a5edbc9eb75b0f7305c4dca9399b309e7e9d2be62f9ed50f

045a016b903f7adf7723ae5e0add61cef3cc7156a3b92ecc0ab23b156f5bba79

afccfa12a7291508291284fab456364a79066f1bca14372f85e1e503a7ba5dc8

212da09ca68167bc40e86f1c838fe5aeb5a6656da5ecbbdb5d17df01b2c262d8

99f1ac661fd45048029818ec876ec7f69228170ea117ffcaef42fd5838f239ac

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-ssl (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-ssl across your stack and pipelines.
If you installed it — respond
aiohttp-ssl 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-ssl 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-ssl 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-ssl 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-055852025-10-asynhttpRLUA-2026-00044

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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