Advisory

RUSTSEC-2026-0039

Also known as: None

Summary

chrono_anchor was removed from crates.io due to malicious code

Details

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][socket] for reporting this crate. They have published
[a blog post][blog] about this recent campaign, and we advise users of
timeapi.io to exercise caution when using crates to interact with that
service.

[socket]: https://socket.dev
[blog]: https://socket.dev/blog/5-malicious-rust-crates-posed-as-time-utilities-to-exfiltrate-env-files

Severity

Not rated by the source.

Dates

Published
2026-03-10 12:00 UTC
Modified
2026-03-17 22:45 UTC

Affected packages and fixes

chrono_anchor

crates.io · All systems

Affected

  • introduced 0.0.0-0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences