Rust advisories / rands
VulnerabilityRUSTSEC-2025-0155 · rands
RUSTSEC-2025-0155: `rands` was removed from crates.io for malicious code
Short answerA security vulnerability in the rands crate: `rands` was removed from crates.io for malicious code. No severity score was published. No fixed version: replace the crate or remove the affected code path.
| Crate | rands |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2025-02-10 |
| Last changed | 2026-03-26 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i rands. - Avoid the affected API, or replace the crate.
Details from the advisory
This crate attempted to typosquat the rand crate, and would link in a malware payload on macOS and Linux hosts when built.
This advisory is to retrospectively document this attempted attack. The version information and download records of the malicious crate are no longer available. The related malicious crates have been yanked, and the malicious account has been banned.
References
- Package: crates.io/crates/rands
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0155.html
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?