RUSTSEC-2026-0028

Source
https://rustsec.org/advisories/RUSTSEC-2026-0028
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0028.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2026-0028
Published
2026-02-26T12:00:00Z
Modified
2026-02-26T21:41:55.789348Z
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.

Database specific
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / tracing_checks

Package

Name
tracing_checks
View open source insights on deps.dev
Purl
pkg:cargo/tracing_checks

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0

Ecosystem specific

{
    "affected_functions": null,
    "affects": {
        "functions": [],
        "os": [],
        "arch": []
    }
}

Database specific

categories
[]
cvss
null
informational
null
source
"https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0028.json"