Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0027 json

`tracings` was removed from crates.io for 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. The only crate depending on this crate was the `tracing_checks` crate, which was also part of this campaign and 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-0027 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 Fencer

Affected packages

ecosystem package affected fixed in
crates.io tracings
>=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.