RUSTSEC-2026-0028 json
`tracing_checks` was removed from crates.io for transitively including malicious code
published 8mo ago modified 7mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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, both in terms of downloads and dependents. It did not include the malware payload itself; this was instead delivered via the `tracings` crate, which 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.
Is RUSTSEC-2026-0028 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | tracing_checks | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.