# 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.

- **Severity:** Not scored
- **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 available:** No
- **Published:** 24 Feb 2026
- **Also known as:** RUSTSEC-2026-0019

## 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`](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.

## Which versions are affected by GHSA-5pmp-jpcf-pwx6?

3 open source packages ship an affected version, including tracing-check.


| Package | Ecosystem | 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.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5pmp-jpcf-pwx6 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of GHSA-5pmp-jpcf-pwx6 in the wild and no public exploit code.

Affected packages and fixed versions:
- tracing-check (crates.io): affected all versions; no fix listed
- tracing-check (crates.io): affected all versions; no fix listed
- tracing-check (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-5pmp-jpcf-pwx6/ (Markdown: https://insights.sbomify.com/GHSA-5pmp-jpcf-pwx6/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5pmp-jpcf-pwx6

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5pmp-jpcf-pwx6/
Summaries are generated and may contain mistakes; the official description above is the record.