Advisory

RUSTSEC-2026-0028

Also known as: None

Summary

tracing_checks was removed from crates.io for transitively including malicious code

Details

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.

Severity

Not rated by the source.

Dates

Published
2026-02-26 12:00 UTC
Modified
2026-03-17 22:45 UTC

Affected packages and fixes

tracing_checks

crates.io · All systems

Affected

  • introduced 0.0.0-0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences