Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io

GHSA-382q-fpqh-29f7

`polymarket-clients-sdk` was removed from crates.io for malicious code

Also known asRUSTSEC-2026-0010
Published
Feb 6, 2026
Updated
Feb 23, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Blast Radius

1 pkg affected
🦀polymarket-clients-sdk

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

It appeared to be typosquatting existing crate polymarket-client-sdk (clients vs client) and attempting to steal credentials from local files.

The malicious crate had 6 versions published on 2026-02-05 and had been downloaded only 59 times. There were no crates depending on this crate on crates.io.

Polymarket thanks Socket.dev for detecting and reporting this to the crates.io team!

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iopolymarket-clients-sdkall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for polymarket-clients-sdk. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of polymarket-clients-sdk has shipped for GHSA-382q-fpqh-29f7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-382q-fpqh-29f7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-382q-fpqh-29f7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

It appeared to be typosquatting existing crate [`polymarket-client-sdk`](https://crates.io/crates/polymarket-client-sdk) (`clients` vs `client`) and attempting to steal credentials from local files. The malicious crate had 6 versions published on 2026-02-05 and had been downloaded only 59 times. There were no crates depending on this crate on crates.io. Polymarket thanks [Socket.dev](https://socket.dev/) for detecting and reporting this to the crates.io team!
O3 Security · Impact-Aware SCA

Is GHSA-382q-fpqh-29f7 in your dependencies?

O3 detects GHSA-382q-fpqh-29f7 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.