Rust advisories / time-sync
Vulnerability CriticalRUSTSEC-2026-0036 · time-sync
RUSTSEC-2026-0036: `time-sync` was removed from crates.io due to malicious code
Short answerA security vulnerability in the time-sync crate: `time-sync` was removed from crates.io due to malicious code. GitHub rates it Critical. No fixed version: replace the crate or remove the affected code path.
| Crate | time-sync |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Critical (GitHub rating) |
| Published | 2026-03-04 |
| Last changed | 2026-03-17 |
| Also known as | GHSA-mh23-rw7f-v5pq |
What to do
- Find who pulls it in:
cargo tree -i time-sync. - Avoid the affected API, or replace the crate.
Details from the advisory
The time-sync crate attempted to exfiltrate .env files to a server that was in turn impersonating the legitimate timeapi.io service. This the same attack that we've seen three times in the last few days.
The malicious crate had 1 version published on 2026-03-04 approximately 50 minutes before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io.
References
- Package: crates.io/crates/time-sync
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0036.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.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?