GHSA-5grr-72f9-678v — cipherbcrypt
Fix: pypa/advisory-database@f8df7b7GHSA-5grr-72f9-678v is a security vulnerability in cipherbcrypt. No vendor fix is recorded yet; mitigation options are listed below.
Malware package cipherbcrypt
Real-World Exposure
cipherbcryptReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Malicious package. Exfiltrated secrets to a target server.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | cipherbcrypt | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cipherbcrypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of cipherbcrypt has shipped for GHSA-5grr-72f9-678v yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5grr-72f9-678v can be triaged on real exposure rather than presence alone.
Tailored to GHSA-5grr-72f9-678v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-5grr-72f9-678v in your dependencies?
O3 Security finds GHSA-5grr-72f9-678v across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.