How severe is GHSA-xhw7-jhmp-j62j?

No CVSS score has been assigned to GHSA-xhw7-jhmp-j62j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xhw7-jhmp-j62j?

GHSA-xhw7-jhmp-j62j affects the following packages: dnp3times (crates.io). Ecosystems affected: crates.io.

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

The records we use list no patched version of dnp3times for GHSA-xhw7-jhmp-j62j. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-xhw7-jhmp-j62j in my crates.io dependencies?

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

How do I mitigate GHSA-xhw7-jhmp-j62j if there is no patch (or I can't update yet)?

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.

Is GHSA-xhw7-jhmp-j62j actively exploited in the wild?

No public exploit code has been indexed for GHSA-xhw7-jhmp-j62j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-xhw7-jhmp-j62j published, and has it been updated?

GHSA-xhw7-jhmp-j62j was published on March 5, 2026 and was last updated on March 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

`dnp3times` was removed from crates.io due to malicious codeGHSA-xhw7-jhmp-j62j

GHSA-xhw7-jhmp-j62j is a security vulnerability in dnp3times. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2026-0032

Published

Mar 5, 2026

Updated

Mar 5, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Mar 5, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀dnp3times

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 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 recent time_calibrator and time_calibrators malware.

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`dnp3times`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dnp3times, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of dnp3times for GHSA-xhw7-jhmp-j62j. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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.

Frequently Asked Questions

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 recent `time_calibrator` and `time_calibrators` malware. 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.

O3 Security · Impact-Aware SCA

Is GHSA-xhw7-jhmp-j62j in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works