Rust advisories / lazystatic
VulnerabilityRUSTSEC-2023-0097 · lazystatic
RUSTSEC-2023-0097: `lazystatic` was removed from crates.io for malicious code
Short answerA security vulnerability in the lazystatic crate: `lazystatic` 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 | lazystatic |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2023-08-16 |
| Last changed | 2026-03-19 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i lazystatic. - 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 amaperf 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 Veracode (formerly phylum)for reporting this to the crates.io team!
References
- Package: crates.io/crates/lazystatic
- Advisory: rustsec.org/advisories/RUSTSEC-2023-0097.html
- Web: www.veracode.com/blog/rust-malware-staged-on-crates-io/
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?