Which versions of http-query are malicious?

The following PyPI versions of http-query are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate http-query if I installed it?

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

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

Yes — http-query is associated with the RLMA-2024-11061, GENERIC-questionable-pentest, RLUA-2026-00395 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 http-query 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 http-query (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging http-query across your stack and pipelines.

Malicious package

http-queryPyPI

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

MAL-2024-11608

Immediate action

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

pip uninstall http-query

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

0b00a058201446f793a0f01b978a58eadeb1204f1f9661deb9e684593bb1035f

e47401149257c6a429be86471416a6d54d8ba266e64f4d90418c2c7281a09f02

f19b11d590534cc47f47b9fc60fae3affd054b1f5dc720dbbc17147cc7095653

3da63914acb2fba33b54b82725f54c5c64215361df70394ccf7f57e61cb19abe

47b0ad63589dbc2e21cbc6e180b1ff725b5744a2cb51b75df6c9e4b42eac01a5

9394e836c97721fa0d5ac0b6dd9c2bc5105ec3f35cd4dae2395b5268243a4362

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

Campaign

RLMA-2024-11061GENERIC-questionable-pentestRLUA-2026-00395

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks http-query-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