# GHSA-xhw7-jhmp-j62j: `dnp3times` was removed from crates.io due to malicious code

> Malicious Rust crate exfiltrated environment files; developers should avoid installing this 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-0032

## What is GHSA-xhw7-jhmp-j62j?

GHSA-xhw7-jhmp-j62j is a vulnerability in dnp3times, 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 `dnp3times` crate attempted to exfiltrate `.env` files to a server
that was in turn impersonating the legitimate `timeapi.io` service. It was
loosely trying to typosquat the `dnp3time` crate, but otherwise was the same
attack as the `time_calibrator` and `time_calibrators` malware yesterday.

The malicious crate had 1 version published on 2026-03-04 approximately 6 hours
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-xhw7-jhmp-j62j?

3 open source packages ship an affected version, including dnp3times.


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

## How do I fix GHSA-xhw7-jhmp-j62j?

No fix has been published for GHSA-xhw7-jhmp-j62j yet. Limit exposure of the affected software until one is available.

## Is GHSA-xhw7-jhmp-j62j being exploited?

There is no known exploitation of GHSA-xhw7-jhmp-j62j in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-xhw7-jhmp-j62j and fix it if it is affected.

What it is: GHSA-xhw7-jhmp-j62j is a vulnerability in dnp3times, 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-xhw7-jhmp-j62j in the wild and no public exploit code.

Affected packages and fixed versions:
- dnp3times (crates.io): affected all versions; no fix listed
- dnp3times (crates.io): affected all versions; no fix listed
- dnp3times (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-xhw7-jhmp-j62j/ (Markdown: https://insights.sbomify.com/GHSA-xhw7-jhmp-j62j/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-xhw7-jhmp-j62j

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