GHSA-f8h5-x737-x4xr json
`finch-rust` was removed from crates.io for malicious code
published 11mo ago modified 7mo ago also RUSTSEC-2025-0148
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
It depended on the `sha-rust` crate, which appeared to be attempting to steal credentials from local files.
Is GHSA-f8h5-x737-x4xr in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | finch-rust | all versions >=0.0.0-0 |
no fix listed |
References
-
blog.rust-lang.org
/2025/12/05/crates.io-malicious-crates-finch-rust-and-sha-rust
web
-
rustsec.org
/advisories/RUSTSEC-2025-0148.html
web, advisory
-
crates.io
/crates/finch-rust
package
-
blog.rust-lang.org
/2025/12/05/crates.io-malicious-crates-finch-rust-and-sha-rust/
web
-
socket.dev
/blog/malicious-crate-mimicking-finch-exfiltrates-credentials
web
Sources
- GitHub Advisory GHSA-f8h5-x737-x4xr
- OSV RUSTSEC-2025-0148
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.