GHSA-5pmp-jpcf-pwx6: Tracing check `tracing-check` Was Removed From Crates.io Vulnerability

CRITICAL
Share
Published
Advisory Summary

GHSA-5pmp-jpcf-pwx6 is a CRITICAL `tracing-check` was removed from crates.io vulnerability (General Security Weakness) affecting Tracing check libraries in the crates.io ecosystem. The issue involves `tracing-check` was removed from crates.io for malicious code. Remediation is available in the latest vendor maintenance releases.

GHSA-5pmp-jpcf-pwx6 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-5pmp-jpcf-pwx6
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Tracing check
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-5pmp-jpcf-pwx6

To remediate this vulnerability, upgrade all affected Tracing check dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

tracing-check fixed: Latest secure release 
Upgrade tracing-check to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for tracing-check

How to Check if You Are Affected

To determine whether your application is affected by GHSA-5pmp-jpcf-pwx6, inspect your project dependencies for Tracing check:

inspect dependencies for tracing-check

Analyze the terminal output to locate any version of Tracing check in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Tracing check, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

This is part of an ongoing campaign to attempt to typosquat crates in the [`polymarket-client-sdk`](https://crates.io/crates/polymarket-client-sdk) ecosystem to exfiltrate user credentials. The malicious crate had 1 version published on 2026-02-24 approximately 4 hours before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io. 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.

GHSA-5pmp-jpcf-pwx6 Affected Tracing check Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
tracing-check
 crates.io

References

Tracing check Source Repository REPOSITORY
https://github.com/polymarket/rs-clob-client
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2026-0019.html

Frequently Asked Questions

What is GHSA-5pmp-jpcf-pwx6?
GHSA-5pmp-jpcf-pwx6 is a security vulnerability in Tracing check involving `tracing-check` was removed from crates.io for malicious code under General Security Weakness.
Which Tracing check versions are affected?
Affected versions include releases prior to current release patches across affected packages: tracing-check.
What version fixes GHSA-5pmp-jpcf-pwx6?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is tracing-check affected?
Yes, tracing-check is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-5pmp-jpcf-pwx6?
GHSA-5pmp-jpcf-pwx6 is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-5pmp-jpcf-pwx6?
Run the dependency tree command: 'inspect dependencies for tracing-check'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5pmp-jpcf-pwx6",
  "modified" : "2026-03-02T18:30:52Z",
  "published" : "2026-03-02T18:30:52Z",
  "aliases" : [ ],
  "summary" : "`tracing-check` was removed from crates.io for malicious code",
  "details" : "This is part of an ongoing campaign to attempt to typosquat crates in the [`polymarket-client-sdk`](https://crates.io/crates/polymarket-client-sdk) ecosystem to exfiltrate user credentials.\n\nThe malicious crate had 1 version published on 2026-02-24 approximately 4 hours before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io.\n\nThe 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.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "tracing-check"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "PACKAGE",
    "url" : "https://github.com/polymarket/rs-clob-client"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2026-0019.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-02T18:30:52Z",
    "nvd_published_at" : null
  }
}