Which versions of bq-build-probe-vrp-2026 are malicious?

The following PyPI versions of bq-build-probe-vrp-2026 are flagged malicious: 0.2.0. Treat any of these as compromised.

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

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

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

Yes — bq-build-probe-vrp-2026 is associated with the IN-MAL-2026-019893 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-build-probe-vrp-2026 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-build-probe-vrp-2026 (version 0.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bq-build-probe-vrp-2026 across your stack and pipelines.

Malicious package

bq-build-probe-vrp-2026PyPI

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

Malicious code in bq-build-probe-vrp-2026 (PyPI)

MAL-2026-16098

Immediate action

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

pip uninstall bq-build-probe-vrp-2026

What this malware does

setup.py executes at pip install and collects a full dump of os.environ, hostname, uid/gid, uname output, /proc/self/cgroup, /proc/version, and the GCE metadata service-account email (http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/email), plus sandbox-fingerprinting signals (docker socket presence at /var/run/docker.sock, outbound reachability via socket connect to 8.8.8.8:53). The collected data is written to _build_findings.json inside the installed package, and init.py exposes get_build_findings() to read it back. In a CI/build environment, os.environ typically contains build secrets (CI tokens, cloud credentials, service-account material); embedding that dump inside the built artifact and providing a retrieval API turns any subsequent import or redistribution of the wheel into a channel for the harvested secrets. The package's self-description as authorized VRP testing does not change the mechanism.

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

46dd2007aa00f3bcd8ad6c767a4f1bf2da7ee75cf91d5b692aec39c546cc1d65

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

Campaign

IN-MAL-2026-019893

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

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