RUSTSEC-2026-0028 `tracing_checks` was removed from crates.io for transitively including malicious code
A malicious crate was published to steal Polymarket credentials, requiring developers to audit dependencies for supply chain risks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is RUSTSEC-2026-0028?
RUSTSEC-2026-0028 is a vulnerability in tracing_checks, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Which versions are affected by RUSTSEC-2026-0028?
1 open source package ship an affected version, including tracing_checks.
| Package | Affected | Fixed in |
|---|---|---|
tracing_checks crates.io | From 0.0.0-0 | None |
How do I fix RUSTSEC-2026-0028?
No fix has been published for RUSTSEC-2026-0028 yet. Limit exposure of the affected software until one is available.
Is RUSTSEC-2026-0028 being exploited?
There is no known exploitation of RUSTSEC-2026-0028 in the wild and no public exploit code.