Rust advisories / tracings
VulnerabilityRUSTSEC-2026-0027 · tracings
RUSTSEC-2026-0027: `tracings` was removed from crates.io for malicious code
Short answerA security vulnerability in the tracings crate: `tracings` 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 | tracings |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2026-02-26 |
| Last changed | 2026-03-17 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i tracings. - Avoid the affected API, or replace the crate.
Details from the advisory
This is part of an ongoing campaign to attempt to typosquat crates in an attempt to exfiltrate Polymarket credentials.
The malicious crate had 1 version published on 2026-02-26 approximately 9 hours before removal and had no evidence of actual usage. The only crate depending on this crate was the tracing_checks crate, which was also part of this campaign and has received a separate advisory.
Thanks to Marko Ćupić for finding and reporting this to the Rust security response working group, and to Emily Albini for co-ordinating with the crates.io team.
The crates.io team advises anyone developing with Polymarket to review dependencies carefully. We are investigating ways to mitigate this attacker who appears to be very motivated to steal Polymarket credentials.
References
- Package: crates.io/crates/tracings
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0027.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?