Which versions of crelic-bqwheel-52f66a3f1d are malicious?

The following PyPI versions of crelic-bqwheel-52f66a3f1d are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate crelic-bqwheel-52f66a3f1d if I installed it?

crelic-bqwheel-52f66a3f1d 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 crelic-bqwheel-52f66a3f1d — how do I know if it already compromised me?

If crelic-bqwheel-52f66a3f1d 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 crelic-bqwheel-52f66a3f1d part of a known attack campaign?

Yes — crelic-bqwheel-52f66a3f1d is associated with the 2026-10-crelic-bqwheel-52f66a3f1d 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 crelic-bqwheel-52f66a3f1d across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for crelic-bqwheel-52f66a3f1d (version 0.0.1).

Malicious package

crelic-bqwheel-52f66a3f1dPyPI

Advisory published Oct 13, 2026Updated Oct 13, 2026

crelic-bqwheel-52f66a3f1d is a confirmed malicious PyPI package (MAL-2026-17863) 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 crelic-bqwheel-52f66a3f1d (PyPI)

MAL-2026-17863

Immediate action

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

pip uninstall crelic-bqwheel-52f66a3f1d

What this malware does

Package attempts to collect environment variables from a specific environment, self-identified as BigQuery user-defined functions research. The final exfiltration of collected data seems to require the control of the execution environment, supporting the research/pentest claims.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2026-10-crelic-bqwheel-52f66a3f1d

Reasons (based on the campaign):

abuses-pth
exfiltration-env-variables
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0ca34d571eaf519847a961f7da1f203d35f7a3c011f5fd4df3744f50a0615d2e

d4583665a5bfbe548102afc727dccfb09aab21d16c8e3faa47590da72c2c1164

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for crelic-bqwheel-52f66a3f1d (version 0.0.1).
If you installed it — respond
crelic-bqwheel-52f66a3f1d 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 crelic-bqwheel-52f66a3f1d 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. crelic-bqwheel-52f66a3f1d 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

2026-10-crelic-bqwheel-52f66a3f1d

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks crelic-bqwheel-52f66a3f1d-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