Which versions of bfox-build-utils are malicious?

The following PyPI versions of bfox-build-utils are flagged malicious: 1.0.997. Treat any of these as compromised.

How do I remediate bfox-build-utils if I installed it?

bfox-build-utils 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 bfox-build-utils — how do I know if it already compromised me?

If bfox-build-utils 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 bfox-build-utils part of a known attack campaign?

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

Malicious package

bfox-build-utilsPyPI

bfox-build-utils is a confirmed malicious PyPI package (MAL-2026-17319) that steals credentials and exfiltrates sensitive data (malicious version 1.0.997). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bfox-build-utils (PyPI)

MAL-2026-17319

Immediate action

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

pip uninstall bfox-build-utils

What this malware does

At install time, setup.py harvests the installer's GitHub credential and uses it to modify the installer's own repository. The script reads $GITHUB_WORKSPACE/.git/config, regexes the extraheader = AUTHORIZATION: basic <b64> line that actions/checkout injects for the running job, base64-decodes it to recover the token, and also reads GITHUB_TOKEN from the environment. Using that token as x-access-token, it clones the installer's repository, creates branch feature/ci-health-check, writes .github/workflows/ci-health-check.yml, commits as github-actions[bot] with message Add CI health check, and pushes via git (with a REST-API fallback), explicitly bypassing the API restriction that protects workflow files. This plants a persistent, attacker-controlled GitHub Actions workflow in the installer's repository that will execute on future pushes to the planted branch. The shipped Python module bfox_build_utils.py is a two-line stub containing only VERSION = "1.0.997"; the package's advertised purpose (Build utilities.) and the innocuous naming of the branch, commit, and bot identity are cover for the credential theft and workflow-injection payload in setup.py.

Malicious versions

1 flagged

1.0.997

Indicators of compromise (SHA-256)

cae53348f8261653938b39ae3cb79101baff666c4216ecaeb635e34b42ba8293

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

Campaign

IN-MAL-2026-020795

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bfox-build-utils-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