{"answers":{"affected":"1 open source package ship an affected version, including tracing_checks.","exploited":"There is no known exploitation of RUSTSEC-2026-0028 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0028 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0028 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of RUSTSEC-2026-0028 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tracing_checks (crates.io): affected from 0.0.0-0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0028/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0028/index.md)","id":"RUSTSEC-2026-0028","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0028/index.md","name":"RUSTSEC-2026-0028","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust crate","requires_auth":"none","summary":"A malicious crate was published to steal Polymarket credentials, requiring developers to audit dependencies for supply chain risks.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This is part of an ongoing campaign to attempt to typosquat crates in an\nattempt to exfiltrate Polymarket credentials.\n\nThe malicious crate had 1 version published on 2026-02-26 approximately 9 hours\nbefore removal and had no evidence of actual usage, both in terms of downloads\nand dependents. It did not include the malware payload itself; this was instead\ndelivered via the `tracings` crate, which has received a separate advisory.\n\nThanks to Marko Ćupić for finding and reporting this to the Rust security\nresponse working group, and to Emily Albini for co-ordinating with the\ncrates.io team.\n\nThe crates.io team advises anyone developing with Polymarket to review\ndependencies carefully. We are investigating ways to mitigate this attacker who\nappears to be very motivated to steal Polymarket credentials.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"`tracing_checks` was removed from crates.io for transitively including malicious code","id":"RUSTSEC-2026-0028","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"tracing_checks","purl":"pkg:cargo/tracing_checks","source":"RUSTSEC-2026-0028"}],"products":null,"published":"2026-02-26","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A malicious crate was published to steal Polymarket credentials, requiring developers to audit dependencies for supply chain risks.","url":"https://insights.sbomify.com/RUSTSEC-2026-0028/"}