RUSTSEC-2026-0027

Source
https://rustsec.org/advisories/RUSTSEC-2026-0027
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0027.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2026-0027
Published
2026-02-26T12:00:00Z
Modified
2026-02-26T21:40:54.551750Z
Summary
`tracings` was removed from crates.io for 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. 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.

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

Affected packages

crates.io / tracings

Package

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0

Ecosystem specific

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

Database specific

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