How severe is GHSA-6662-54xr-8423?

No CVSS score has been assigned to GHSA-6662-54xr-8423 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6662-54xr-8423?

GHSA-6662-54xr-8423 affects the following packages: evm-units (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-6662-54xr-8423?

The records we use list no patched version of evm-units for GHSA-6662-54xr-8423. 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-6662-54xr-8423 in my crates.io dependencies?

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

How do I mitigate GHSA-6662-54xr-8423 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-6662-54xr-8423 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6662-54xr-8423 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-6662-54xr-8423 published, and has it been updated?

GHSA-6662-54xr-8423 was published on February 6, 2026 and was last updated on February 23, 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

`evm-units` was removed from crates.io for malicious codeGHSA-6662-54xr-8423

GHSA-6662-54xr-8423 is a security vulnerability in evm-units. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0147

Published

Feb 6, 2026

Updated

Feb 23, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Feb 23, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀evm-units

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

It appeared to be attempting to steal cryptocurrency.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`evm-units`	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 evm-units, 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 evm-units for GHSA-6662-54xr-8423. 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

It appeared to be attempting to steal cryptocurrency.

O3 Security · Impact-Aware SCA

Is GHSA-6662-54xr-8423 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works