How severe is GHSA-5pmp-jpcf-pwx6?

No CVSS score has been assigned to GHSA-5pmp-jpcf-pwx6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5pmp-jpcf-pwx6?

GHSA-5pmp-jpcf-pwx6 affects the following packages: tracing-check (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-5pmp-jpcf-pwx6?

The records we use list no patched version of tracing-check for GHSA-5pmp-jpcf-pwx6. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-5pmp-jpcf-pwx6 in my crates.io dependencies?

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.

How do I mitigate GHSA-5pmp-jpcf-pwx6 if there is no patch (or I can't update yet)?

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.

Is GHSA-5pmp-jpcf-pwx6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5pmp-jpcf-pwx6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5pmp-jpcf-pwx6 published, and has it been updated?

GHSA-5pmp-jpcf-pwx6 was published on March 2, 2026 and was last updated on March 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

`tracing-check` was removed from crates.io for malicious codeGHSA-5pmp-jpcf-pwx6

GHSA-5pmp-jpcf-pwx6 is a security vulnerability in tracing-check. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2026-0019

Published

Mar 2, 2026

Updated

Mar 5, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Mar 5, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀tracing-check

Real-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

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`tracing-check`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
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
The records we use list no patched version of tracing-check for GHSA-5pmp-jpcf-pwx6. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-5pmp-jpcf-pwx6 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works