Mediumcrates.io1 affected version

time_calibrator

time_calibrator has 1 version on crates.io flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with cargo tree -i time_calibrator.

time_calibrator@0.1.0

The incident that flagged it

Medium28 Feb 2026

5 malicious Rust crates pose as time utilities to exfiltrate .env files

Five crates published between late February and early March 2026 posed as local time utilities while exfiltrating .env files via curl to a lookalike domain timeapis.io (typosquatting timeapi.io). All packages were 0.1.0 and yanked within hours. Account aliases: gehakax777, dictorudin.

Versions named here: 0.1.0

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

time_calibrator is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse crates.io manifests yet, but the incident write-ups list every affected package.

Browse the incident feed All flagged crates.io packages

Other packages in the same incident

If time_calibrator is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.