Rust advisories / chrono_anchor
VulnerabilityRUSTSEC-2026-0039 · chrono_anchor
RUSTSEC-2026-0039: `chrono_anchor` was removed from crates.io due to malicious code
Short answerA security vulnerability in the chrono_anchor crate: `chrono_anchor` was removed from crates.io due to malicious code. No severity score was published. No fixed version: replace the crate or remove the affected code path.
| Crate | chrono_anchor |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2026-03-10 |
| Last changed | 2026-03-17 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i chrono_anchor. - Avoid the affected API, or replace the crate.
Details from the advisory
The chrono_anchor crate attempted to exfiltrate .env files to a server that was in turn impersonating the legitimate timeapi.io service.
The malicious crate had 1 version published on 2026-03-04 approximately 6 days before removal and had no evidence of actual downloads. There were no crates depending on this crate on crates.io.
Thanks to Socket for reporting this crate. They have published a blog post about this recent campaign, and we advise users of timeapi.io to exercise caution when using crates to interact with that service.
References
- Package: crates.io/crates/chrono_anchor
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0039.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?