Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-mh23-rw7f-v5pq time-sync

GHSA-mh23-rw7f-v5pq is a security vulnerability in time-sync. No vendor fix is recorded yet; mitigation options are listed below.

`time-sync` was removed from crates.io due to malicious code

Also known asRUSTSEC-2026-0036
Published
Mar 5, 2026
Updated
Mar 6, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Mar 6, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀time-sync

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iotime-syncall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for time-sync, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of time-sync has shipped for GHSA-mh23-rw7f-v5pq yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mh23-rw7f-v5pq can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mh23-rw7f-v5pq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-mh23-rw7f-v5pq in your dependencies?

O3 Security finds GHSA-mh23-rw7f-v5pq across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-mh23-rw7f-v5pq: time-sync | O3 Security