GHSA-5pmp-jpcf-pwx6: `tracing-check` was removed from crates.io for malicious code
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.
Published Mar 2, 2026
Affected packages
tracing-check
- Ecosystem
- Rust (crates.io)
- Affected
- >= 0
- Fixed in
- No patched version yet
- Check
cargo tree -i tracing-check
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology