RUSTSEC-2026-0018
`rpc-check` was removed from crates.io for malicious code
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.
What each source reports
OSV No score
`rpc-check` was removed from crates.io for malicious code
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.
- Record
RUSTSEC-2026-0018- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
rpc-checkcrates.io |
0.0.0-0 and later | None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
RUSTSEC-2026-0018 is a vulnerability with no CVSS score yet in rpc-check, published February 24, 2026. No source lists public exploit code. No source names a fixed version.