GHSA-5pmp-jpcf-pwx6 — tracing-check
GHSA-5pmp-jpcf-pwx6 is a security vulnerability in tracing-check. No vendor fix is recorded yet; mitigation options are listed below.
`tracing-check` was removed from crates.io for malicious code
Real-World Exposure
tracing-checkReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
This is part of an ongoing campaign to attempt to typosquat crates in the 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | tracing-check | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tracing-check, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of tracing-check has shipped for GHSA-5pmp-jpcf-pwx6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5pmp-jpcf-pwx6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-5pmp-jpcf-pwx6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-5pmp-jpcf-pwx6 in your dependencies?
O3 Security finds GHSA-5pmp-jpcf-pwx6 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.