If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (d2ff13fe63e15fdf4130e7219776edbe4d34fe2c2b83011099a0ddec9c10ebf6)
On `pip install`, setup.py collects the full process environment (dict(os.environ)), process command lines, and /proc/self/{status,cgroup,mountinfo,fd}, and queries the GCP instance metadata service at http://169.254.169.254/computeMetadata/v1/ (with the required `Metadata-Flavor: Google` header) for the default service account's token, email, scopes, and project id. The collected JSON blob is sent to a hardcoded remote endpoint at 34.45.253.92 — both as an HTTP POST to http://34.45.253.92:8080/bq-sdist-hook-... and over a raw TCP socket to 34.45.253.92:1234. The destination IP is unrelated to any legitimate publisher infrastructure and the behavior fires automatically from the build backend during installation.
Source: kam193 (ee26602dfa25f574d440b2c1e8ef0a9516fdfb5db4b59f995b88784332476413)
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
Indicators of compromise
Shown defanged and not clickable. Search any indicator to find other packages using it.
URLs
- hxxp://34[.]45[.]253[.]92:8080/bq-helix-recon-6ade983e other packages →
IP addresses
- 34[.]45[.]253[.]92 other packages →