Rust advisories / tracing-check
Vulnerability CriticalRUSTSEC-2026-0019 · tracing-check
RUSTSEC-2026-0019: `tracing-check` was removed from crates.io for malicious code
Short answerA security vulnerability in the tracing-check crate: `tracing-check` was removed from crates.io for malicious code. GitHub rates it Critical. No fixed version: replace the crate or remove the affected code path.
| Crate | tracing-check |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Critical (GitHub rating) |
| Published | 2026-02-24 |
| Last changed | 2026-03-17 |
| Also known as | GHSA-5pmp-jpcf-pwx6 |
What to do
- Find who pulls it in:
cargo tree -i tracing-check. - 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 the polymarket-client-sdk ecosystem to exfiltrate user credentials.
The malicious crate had 1 version published on 2026-02-24 approximately 4 hours before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io.
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/tracing-check
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0019.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?