Which versions of bq-sdist-probe-vrp are malicious?

The following PyPI versions of bq-sdist-probe-vrp are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate bq-sdist-probe-vrp if I installed it?

bq-sdist-probe-vrp 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 bq-sdist-probe-vrp — how do I know if it already compromised me?

If bq-sdist-probe-vrp 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 bq-sdist-probe-vrp part of a known attack campaign?

Yes — bq-sdist-probe-vrp is associated with the IN-MAL-2026-019894 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 bq-sdist-probe-vrp 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 bq-sdist-probe-vrp (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 bq-sdist-probe-vrp across your stack and pipelines.

Malicious package

bq-sdist-probe-vrpPyPI

bq-sdist-probe-vrp is a confirmed malicious PyPI package (MAL-2026-16099) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bq-sdist-probe-vrp (PyPI)

MAL-2026-16099

Immediate action

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

pip uninstall bq-sdist-probe-vrp

What this malware does

setup.py executes at pip install time and performs installer-side credential and host reconnaissance. It queries the GCE/GCP metadata service at http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token with the Metadata-Flavor: Google header to obtain the default service account's OAuth access token, service account email, and project id. It also filters os.environ for keys containing token, secret, key, pass, auth, google, project, docker, kube, or metadata substrings, and collects hostname, uid/gid/pid, the output of the id command, os.uname(), /proc/version, os.listdir('/'), and checks for /var/run/docker.sock. It performs an outbound TCP connect to 8.8.8.8:53 to test network reachability. The collected data is persisted to a JSON file inside the installed package directory. Naming (bq-sdist-probe-vrp) and behavior are consistent with a probe that harvests installer-owned cloud credentials in CI/build environments.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f61d3e118672e10f0dc02115acd8235c3b356d75e7cb59a69e26fec28070c814

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 bq-sdist-probe-vrp (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 bq-sdist-probe-vrp across your stack and pipelines.
If you installed it — respond
bq-sdist-probe-vrp 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 bq-sdist-probe-vrp 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 bq-sdist-probe-vrp 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. bq-sdist-probe-vrp 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

IN-MAL-2026-019894

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bq-sdist-probe-vrp-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

Explore

All malware advisories How O3 detects malware Vulnerability database