Rust advisories / logflux
VulnerabilityRUSTSEC-2026-0171 · logflux
RUSTSEC-2026-0171: `logflux` was removed from crates.io for malicious code
Short answerA security vulnerability in the logflux crate: `logflux` 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 | logflux |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2026-06-03 |
| Last changed | 2026-06-04 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i logflux. - Avoid the affected API, or replace the crate.
Details from the advisory
The logflux crate attempted to download and run a malicious payload on the user's machine.
The malicious crate had 1 version published on 2026-04-26, approximately 1 month before removal, and had no evidence of actual usage. This crate had no dependencies on crates.io.
Thanks to Paweł Bis for discovering and reporting this crate!
This appears to have been part of a campaign targeting people applying for Rust jobs. Please be careful with take-home assignments, especially if they ask you to use specific dependencies.
References
- Package: crates.io/crates/logflux
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0171.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?