Which versions of bq-helix-build-hook-6ade983e are malicious?

The following PyPI versions of bq-helix-build-hook-6ade983e are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate bq-helix-build-hook-6ade983e if I installed it?

bq-helix-build-hook-6ade983e 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-helix-build-hook-6ade983e — how do I know if it already compromised me?

If bq-helix-build-hook-6ade983e was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is bq-helix-build-hook-6ade983e part of a known attack campaign?

Yes — bq-helix-build-hook-6ade983e is associated with the 2026-10-bq-helix-recon 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-helix-build-hook-6ade983e across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bq-helix-build-hook-6ade983e (version 0.1.0).

Malicious package

bq-helix-build-hook-6ade983ePyPI

Advisory published Oct 29, 2026Updated Oct 29, 2026

bq-helix-build-hook-6ade983e is a confirmed malicious PyPI package (MAL-2026-18395) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bq-helix-build-hook-6ade983e (PyPI)

MAL-2026-18395

Immediate action

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

pip uninstall bq-helix-build-hook-6ade983e

What this malware does

During installation the code collects information from the environment, including credential files, environment variables, data from cloud metadata endpoints, and finally exfiltrates them.

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

Campaign: 2026-10-bq-helix-recon

Reasons (based on the campaign):

abuses-pth
exfiltration-cloud-tokens
exfiltration-generic
exfiltration-env-variables
exfiltration-credentials

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

ee26602dfa25f574d440b2c1e8ef0a9516fdfb5db4b59f995b88784332476413

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for bq-helix-build-hook-6ade983e (version 0.1.0).
If you installed it — respond
bq-helix-build-hook-6ade983e 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-helix-build-hook-6ade983e was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bq-helix-build-hook-6ade983e on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-bq-helix-recon

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks bq-helix-build-hook-6ade983e-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