VulnerabilityRUSTSEC-2026-0014 · rpc-check
RUSTSEC-2026-0014: `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-19 |
| 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
It was attempting to steal credentials from the POLYMARKET_PRIVATE_KEY environment variable.
The malicious crate had 3 versions published on 2026-02-15 and had been downloaded only 155 times. There were no crates depending on this crate on crates.io.
Thanks to Sisong Li for finding and reporting this to the crates.io team!
References
- Package: crates.io/crates/rpc-check
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0014.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?