# RUSTSEC-2026-0039: `chrono_anchor` was removed from crates.io due to malicious code

> A malicious Rust crate exfiltrated environment files to an attacker-controlled server, requiring users to remove the package immediately.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2026

## What is RUSTSEC-2026-0039?

RUSTSEC-2026-0039 is a vulnerability in chrono_anchor, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

## Which versions are affected by RUSTSEC-2026-0039?

1 open source package ship an affected version, including chrono_anchor.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `chrono_anchor` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2026-0039?

No fix has been published for RUSTSEC-2026-0039 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2026-0039 being exploited?

There is no known exploitation of RUSTSEC-2026-0039 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0039 and fix it if it is affected.

What it is: RUSTSEC-2026-0039 is a vulnerability in chrono_anchor, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of RUSTSEC-2026-0039 in the wild and no public exploit code.

Affected packages and fixed versions:
- chrono_anchor (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0039/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0039/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0039

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0039/
Summaries are generated and may contain mistakes; the official description above is the record.