Which versions of auohttp are malicious?

The following PyPI versions of auohttp are flagged malicious: 3.13.3. Treat any of these as compromised.

How do I remediate auohttp if I installed it?

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

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

Yes — auohttp is associated with the 2026-01-aiihttp 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 auohttp 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 auohttp (version 3.13.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging auohttp across your stack and pipelines.

Malicious package

auohttpPyPI

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

MAL-2026-38

Immediate action

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

pip uninstall auohttp

What this malware does

Obfuscated code downloads an encrypted binary blob, which is malware finally starting cryptomining. After starting the malware, the Python package uninstall itself and installs the legitimate package, covering tracks of the infection.

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

Campaign: 2026-01-aiihttp

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote executable.
malware
cryptominer
obfuscation
covering-tracks

Malicious versions

1 flagged

3.13.3

Indicators of compromise (SHA-256)

f4b76a407d91e23cb990d6ed08e3c0e81898f2b97d690db76b4e3b547fda5fab

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

Campaign

2026-01-aiihttp

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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