Which versions of asynhttp are malicious?

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

How do I remediate asynhttp if I installed it?

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

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

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

Malicious package

asynhttpPyPI

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

MAL-2025-191619

Immediate action

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

pip uninstall asynhttp

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)

27f648a30d77874cfffeb97c2052d67485ed66da94f30db8cf52415393a89ca0

649f3bd8674eef95a14f9f389db5a8900362ba5f5f18381ffaa885a43395db8a

2c5f91525485110943474c187077da4ab6ef21e3209e4d6e7abf1007321cf1cd

058c3bab076ccb770a3ecaefbdb301df88bd935a79f154cdeb329c51c4a1eef5

d26ba778d37d3f66388d7a6df9468b6b43847d3f998df59716fb385da9a84fc1

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 asynhttp (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 asynhttp across your stack and pipelines.
If you installed it — respond
asynhttp 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 asynhttp 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 asynhttp 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. asynhttp 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-055862025-10-asynhttpRLUA-2026-00093

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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