Which versions of httpx-client are malicious?

The following PyPI versions of httpx-client are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate httpx-client if I installed it?

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

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

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

Malicious package

httpx-clientPyPI

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

MAL-2025-3448

Immediate action

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

pip uninstall httpx-client

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.1

Indicators of compromise (SHA-256)

9ff2d32be1f48fa36bb92be791d851bbd82410dbaff5e4d25129b3f8afac669c

6fdc9cdaef31f88070b3abd593a1854c51a88eba4e915f16c553ce10a5c625fa

d26dbf9fa1035b8b1e189f67123ee22f506cd21c08e17c282176a716af9da033

a0ed7307c7fc2d4cb66bfc22e731e688cabb34b1b8f481e5faa8cd8bae996cb2

87d2fbdf54ffb1b9f5e6d6126bfc59f1e64a6b142880ab859250df371a65d596

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

Campaign

RLMA-2025-025102025-03-httpx-clientRLUA-2026-00403

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks httpx-client-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