VulnerabilityRUSTSEC-2023-0104 · littest
RUSTSEC-2023-0104: `littest` was removed from crates.io for malicious code
Short answerA security vulnerability in the littest crate: `littest` 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 | littest |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2023-11-06 |
| Last changed | 2026-03-26 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i littest. - Avoid the affected API, or replace the crate.
Details from the advisory
This crate was part of a typosquatting malware cluster published by the malicious user http-tiny and contained a malware payload in build.rs to exfiltrate host information to the attacker.
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.
Thanks to Louis Lang at Phylum (now Veracode) for reporting this malware campaign.
References
- Package: crates.io/crates/littest
- Advisory: rustsec.org/advisories/RUSTSEC-2023-0104.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.
Other advisories for littest
Up next
Same cratelittest: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?