Which versions of asynchttpx are malicious?

The following PyPI versions of asynchttpx are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate asynchttpx if I installed it?

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

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

Yes — asynchttpx is associated with the RLMA-2025-02488, 2025-03-httpx-client, RLUA-2026-00090 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 asynchttpx 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 asynchttpx (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging asynchttpx across your stack and pipelines.

Malicious package

asynchttpxPyPI

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

MAL-2025-3429

Immediate action

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

pip uninstall asynchttpx

What this malware does

Importing the module starts downloading and executing first a script, and then a widely identified malware

Packages are used as dependencies in a GitHub project https://github.com/ToolParadiseDrako/Nuker-Tool-Paradise

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

Campaign: 2025-03-httpx-client

Reasons (based on the campaign):

Downloads and executes a remote executable.
Downloads and executes a remote malicious script.
malware

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

d392c3b5b294cf5ed0f8ea36a2218c162f8bdebfb41064bbf49b33c081b8e5eb

06822f2d60049efaf55fc4d913311d71e9ef6bbcbe4e07c79c3f02926fc76665

5b8f233eae76de4578a7b30c6564338d644a7dfa1f59682337792de5ad13668f

449f749aff9ba237639644b326f7475bde98d4aec364d794bfcce51a77e299c9

d4d4f60867a1881d6c44d06bed815b780ccb05ddb5735c0afa0868ee70dd41db

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

Campaign

RLMA-2025-024882025-03-httpx-clientRLUA-2026-00090

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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