# GHSA-5grr-72f9-678v: Malware package cipherbcrypt

> A malicious Python package exfiltrates secrets to an attacker-controlled server, requiring developers to remove it immediately.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2024

## What is GHSA-5grr-72f9-678v?

GHSA-5grr-72f9-678v is a vulnerability in cipherbcrypt, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Malicious package. Exfiltrated secrets to a target server.

## Which versions are affected by GHSA-5grr-72f9-678v?

2 open source packages ship an affected version, including cipherbcrypt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cipherbcrypt` | PyPI | All versions | None |
| `cipherbcrypt` | PyPI | All versions | None |

## How do I fix GHSA-5grr-72f9-678v?

No fix has been published for GHSA-5grr-72f9-678v yet. Limit exposure of the affected software until one is available.

## Is GHSA-5grr-72f9-678v being exploited?

There is no known exploitation of GHSA-5grr-72f9-678v in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5grr-72f9-678v and fix it if it is affected.

What it is: GHSA-5grr-72f9-678v is a vulnerability in cipherbcrypt, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-5grr-72f9-678v in the wild and no public exploit code.

Affected packages and fixed versions:
- cipherbcrypt (PyPI): affected all versions; no fix listed
- cipherbcrypt (PyPI): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-5grr-72f9-678v/ (Markdown: https://insights.sbomify.com/GHSA-5grr-72f9-678v/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5grr-72f9-678v

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5grr-72f9-678v/
Summaries are generated and may contain mistakes; the official description above is the record.