# Polymarket SDK typosquats on crates.io

> Three crates impersonating `polymarket-client-sdk` were published between 5 and 19 February 2026 and exfiltrated local credential files. The malicious crates were yanked and publisher accounts disabled. Combined downloads stayed under 100, but targeting was high-value (Polymarket / Web3 developers).

- Published: 2026-02-05
- Severity: medium
- Kind: Typosquat - A package that never had a legitimate version, named to be mistaken for a real one - a misspelling, a lookalike scope, or an impersonated vendor SDK.
- Ecosystems: crates.io
- Scope: 3 packages, 0 compromised versions
- Tags: typosquat, credential-theft
- Detected by: RustSec
- Incident ID: crates-2026-02-05-polymarket-typosquats

## Affected packages (3)

Only the exact versions listed were named by the source advisories. Other versions are not implicated.

| Package | Ecosystem | Compromised versions |
|---|---|---|
| [polymarket-client-sdks](https://dependencywatch.io/package/crates/polymarket-client-sdks) | crates.io |  |
| [polymarket-clients-sdk](https://dependencywatch.io/package/crates/polymarket-clients-sdk) | crates.io |  |
| [polymarkets-client-sdk](https://dependencywatch.io/package/crates/polymarkets-client-sdk) | crates.io |  |

## What happened

Between February 5 and 19, 2026, three crates impersonating the real Polymarket Rust SDK were published to crates.io: `polymarket-clients-sdk` (extra "s" before the dash), `polymarket-client-sdks` (extra "s" at the end), and `polymarkets-client-sdk` (extra "s" on the first segment). All three lifted documentation from the legitimate package to look credible at install time.

On run, each crate walks the local filesystem for credential files - `.aws/credentials`, `.npmrc`, `id_rsa`, environment files - and posts them to attacker infrastructure. RustSec yanked the crates and disabled the publishing accounts. Combined downloads stayed under 100 across all three, so the absolute exposure is small, but the targeting is deliberate: only Polymarket / Web3 developers would search for that exact package name.

The broader pattern - typosquats of niche, high-value ecosystem clients - is now common enough on crates.io that any project resolving Web3 SDK dependencies should pin to known-good versions and run `cargo-audit` against the RustSec advisory database in CI.

## Impact

- Targeted Polymarket/Web3 developers via deliberate typosquats
- Local credential-file theft from build/dev systems
- Low total downloads but high-value targets

## What to do

1. Audit Cargo.toml + Cargo.lock for the typosquatted names
2. Rotate credentials present on any host that built with these crates
3. Run `cargo-audit` against the RustSec advisory DB in CI

## References

- [RustSec: RUSTSEC-2026-0010](https://rustsec.org/advisories/RUSTSEC-2026-0010.html) - RustSec

---

Canonical page: https://dependencywatch.io/incident/crates-2026-02-05-polymarket-typosquats
Markdown version: https://dependencywatch.io/incident/crates-2026-02-05-polymarket-typosquats.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).