{"answers":{"affected":"3 open source packages ship an affected version, including tracing-check.","exploited":"There is no known exploitation of GHSA-5pmp-jpcf-pwx6 in the wild and no public exploit code.","fix":"No fix has been published for GHSA-5pmp-jpcf-pwx6 yet. Limit exposure of the affected software until one is available.","what":"GHSA-5pmp-jpcf-pwx6 is a vulnerability in tracing-check, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-5pmp-jpcf-pwx6 and fix it if it is affected.\n\nWhat it is: GHSA-5pmp-jpcf-pwx6 is a vulnerability in tracing-check, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-5pmp-jpcf-pwx6 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tracing-check (crates.io): affected all versions; no fix listed\n- tracing-check (crates.io): affected all versions; no fix listed\n- tracing-check (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/GHSA-5pmp-jpcf-pwx6/ (Markdown: https://insights.sbomify.com/GHSA-5pmp-jpcf-pwx6/index.md)","id":"GHSA-5pmp-jpcf-pwx6","markdown":"https://insights.sbomify.com/GHSA-5pmp-jpcf-pwx6/index.md","name":"GHSA-5pmp-jpcf-pwx6","record":{"aliases":["RUSTSEC-2026-0019"],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust crate","requires_auth":"none","summary":"Malicious typosquatting crate exfiltrates credentials if developers accidentally install it instead of the legitimate Polymarket SDK.","user_interaction":"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 the\n[`polymarket-client-sdk`](https://crates.io/crates/polymarket-client-sdk)\necosystem to exfiltrate user credentials.\n\nThe malicious crate had 1 version published on 2026-02-24 approximately 4 hours\nbefore removal and had no evidence of actual downloads. There were no crates\ndepending on this crate on crates.io.\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-check` was removed from crates.io for malicious code","id":"GHSA-5pmp-jpcf-pwx6","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":[],"package":"tracing-check","purl":null,"source":"GHSA-5pmp-jpcf-pwx6"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":[],"package":"tracing-check","purl":"pkg:cargo/tracing-check","source":"GHSA-5pmp-jpcf-pwx6"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"tracing-check","purl":"pkg:cargo/tracing-check","source":"RUSTSEC-2026-0019"}],"products":null,"published":"2026-02-24","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"Malicious typosquatting crate exfiltrates credentials if developers accidentally install it instead of the legitimate Polymarket SDK.","url":"https://insights.sbomify.com/GHSA-5pmp-jpcf-pwx6/"}