# GHSA-mh23-rw7f-v5pq: `time-sync` was removed from crates.io due to malicious code

> A malicious Rust crate exfiltrated environment files to an attacker-controlled server, requiring developers to avoid using the removed package.

- **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:** 4 Mar 2026
- **Also known as:** RUSTSEC-2026-0036

## What is GHSA-mh23-rw7f-v5pq?

GHSA-mh23-rw7f-v5pq is a vulnerability in time-sync, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-mh23-rw7f-v5pq?

3 open source packages ship an affected version, including time-sync.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `time-sync` | crates.io | All versions | None |
| `time-sync` | crates.io | All versions | None |
| `time-sync` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-mh23-rw7f-v5pq?

No fix has been published for GHSA-mh23-rw7f-v5pq yet. Limit exposure of the affected software until one is available.

## Is GHSA-mh23-rw7f-v5pq being exploited?

There is no known exploitation of GHSA-mh23-rw7f-v5pq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-mh23-rw7f-v5pq and fix it if it is affected.

What it is: GHSA-mh23-rw7f-v5pq is a vulnerability in time-sync, published on 4 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 GHSA-mh23-rw7f-v5pq in the wild and no public exploit code.

Affected packages and fixed versions:
- time-sync (crates.io): affected all versions; no fix listed
- time-sync (crates.io): affected all versions; no fix listed
- time-sync (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/GHSA-mh23-rw7f-v5pq/ (Markdown: https://insights.sbomify.com/GHSA-mh23-rw7f-v5pq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-mh23-rw7f-v5pq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-mh23-rw7f-v5pq/
Summaries are generated and may contain mistakes; the official description above is the record.