VulnerabilityRUSTSEC-2026-0018 · rpc-check
RUSTSEC-2026-0018: `rpc-check` was removed from crates.io for malicious code
Short answerA security vulnerability in the rpc-check crate: `rpc-check` was removed from crates.io for malicious code. No severity score was published. No fixed version: replace the crate or remove the affected code path.
| Crate | rpc-check |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2026-02-24 |
| Last changed | 2026-03-17 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i rpc-check. - Avoid the affected API, or replace the crate.
Details from the advisory
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 6 versions published from 2026-02-20 onwards and had no evidence of actual usage. There were no crates depending on this crate on crates.io.
Thanks to Eren for finding and reporting this to the Rust security response working group, and to Emily Albini for co-ordinating with the crates.io team.
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.
References
- Package: crates.io/crates/rpc-check
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0018.html
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for rpc-check
Up next
Same craterpc-check: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?