GHSA-5pmp-jpcf-pwx6 `tracing-check` was removed from crates.io for malicious code
Malicious typosquatting crate exfiltrates credentials if developers accidentally install it instead of the legitimate Polymarket SDK.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is GHSA-5pmp-jpcf-pwx6?
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.
Official 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.
Which versions are affected by GHSA-5pmp-jpcf-pwx6?
3 open source packages ship an affected version, including tracing-check.
| Package | Affected | Fixed in |
|---|---|---|
tracing-check crates.io | All versions | None |
tracing-check crates.io | All versions | None |
tracing-check crates.io | From 0.0.0-0 | None |
How do I fix GHSA-5pmp-jpcf-pwx6?
No fix has been published for GHSA-5pmp-jpcf-pwx6 yet. Limit exposure of the affected software until one is available.
Is GHSA-5pmp-jpcf-pwx6 being exploited?
There is no known exploitation of GHSA-5pmp-jpcf-pwx6 in the wild and no public exploit code.
Sources
Also known as RUSTSEC-2026-0019.