# GHSA-6v2j-vr4h-f632: `finch_cli_rust` was removed from crates.io for malicious code

> A malicious Rust crate typosquatted a legitimate package to steal local credentials, requiring developers to avoid installing it.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Also known as:** RUSTSEC-2025-0152

## What is GHSA-6v2j-vr4h-f632?

GHSA-6v2j-vr4h-f632 is a vulnerability in finch_cli_rust, published on 9 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

This attempts to typosquat the existing crate
[`finch_cli`](https://crates.io/crates/finch_cli) to steal credentials from
local files.

The malicious crate had 1 version published on 2025-12-08 and had been
downloaded 18 times. There were no crates depending on this crate on crates.io.

Thanks to Matthias Zepper of [NGI Sweden](https://ngisweden.scilifelab.se/) for
reporting this to the crates.io team!

## Which versions are affected by GHSA-6v2j-vr4h-f632?

3 open source packages ship an affected version, including finch_cli_rust.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `finch_cli_rust` | crates.io | All versions | None |
| `finch_cli_rust` | crates.io | All versions | None |
| `finch_cli_rust` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-6v2j-vr4h-f632?

No fix has been published for GHSA-6v2j-vr4h-f632 yet. Limit exposure of the affected software until one is available.

## Is GHSA-6v2j-vr4h-f632 being exploited?

There is no known exploitation of GHSA-6v2j-vr4h-f632 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6v2j-vr4h-f632 and fix it if it is affected.

What it is: GHSA-6v2j-vr4h-f632 is a vulnerability in finch_cli_rust, published on 9 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-6v2j-vr4h-f632 in the wild and no public exploit code.

Affected packages and fixed versions:
- finch_cli_rust (crates.io): affected all versions; no fix listed
- finch_cli_rust (crates.io): affected all versions; no fix listed
- finch_cli_rust (crates.io): affected from 0.0.0-0; 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-6v2j-vr4h-f632/ (Markdown: https://insights.sbomify.com/GHSA-6v2j-vr4h-f632/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6v2j-vr4h-f632

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6v2j-vr4h-f632/
Summaries are generated and may contain mistakes; the official description above is the record.