GHSA-mh23-rw7f-v5pq json
`time-sync` was removed from crates.io due to malicious code
published 8mo ago modified 7mo ago also RUSTSEC-2026-0036
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Is GHSA-mh23-rw7f-v5pq in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | time-sync | all versions >=0.0.0-0 |
no fix listed |
References
-
rustsec.org
/advisories/RUSTSEC-2026-0036.html
web, advisory
-
crates.io
/crates/time-sync
package
Sources
- GitHub Advisory GHSA-mh23-rw7f-v5pq
- OSV RUSTSEC-2026-0036
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.