# GHSA-3mmg-7c2q-8938: `sha-rust` was removed from crates.io for malicious code

> The sha-rust crate contained malicious code designed to steal local credentials, requiring immediate removal from projects.

- **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:** 5 Dec 2025
- **Also known as:** RUSTSEC-2025-0146

## What is GHSA-3mmg-7c2q-8938?

GHSA-3mmg-7c2q-8938 is a vulnerability in sha-rust, published on 5 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It appeared to be attempting to steal credentials from local files.

## Which versions are affected by GHSA-3mmg-7c2q-8938?

3 open source packages ship an affected version, including sha-rust.


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

## How do I fix GHSA-3mmg-7c2q-8938?

No fix has been published for GHSA-3mmg-7c2q-8938 yet. Limit exposure of the affected software until one is available.

## Is GHSA-3mmg-7c2q-8938 being exploited?

There is no known exploitation of GHSA-3mmg-7c2q-8938 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3mmg-7c2q-8938 and fix it if it is affected.

What it is: GHSA-3mmg-7c2q-8938 is a vulnerability in sha-rust, published on 5 Dec 2025. 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-3mmg-7c2q-8938 in the wild and no public exploit code.

Affected packages and fixed versions:
- sha-rust (crates.io): affected all versions; no fix listed
- sha-rust (crates.io): affected all versions; no fix listed
- sha-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-3mmg-7c2q-8938/ (Markdown: https://insights.sbomify.com/GHSA-3mmg-7c2q-8938/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3mmg-7c2q-8938

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3mmg-7c2q-8938/
Summaries are generated and may contain mistakes; the official description above is the record.