Which versions of queryservice-client are malicious?

The following PyPI versions of queryservice-client are flagged malicious: 0.1.0, 2.3.2. Treat any of these as compromised.

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

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

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

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

Malicious package

queryservice-clientPyPI

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

MAL-2026-5

Immediate action

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

pip uninstall queryservice-client

What this malware does

Dependency confusion PoC that exfiltrates also potentially sensitive environment variables

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

2 flagged

0.1.02.3.2

Indicators of compromise (SHA-256)

92aafbccc7065760e0127931c5150c59561f3b753ab9fe79dbcbdafd1aef97dc

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

Campaign

GENERIC-questionable-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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