Rust advisories / logtrace
VulnerabilityRUSTSEC-2026-0081 · logtrace
RUSTSEC-2026-0081: `logtrace` was removed from crates.io for malicious code
Short answerA security vulnerability in the logtrace crate: `logtrace` 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 | logtrace |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2026-04-05 |
| Last changed | 2026-04-06 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i logtrace. - Avoid the affected API, or replace the crate.
Details from the advisory
logtrace appeared to be downloading a RAT.
The malicious crate had 2 versions published on 2026-04-01 that had a total of 30 downloads. There were no crates depending on this crate on crates.io.
Thanks to Socket.dev for detecting and reporting this to the crates.io team!
References
- Package: crates.io/crates/logtrace
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0081.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?