How severe is GHSA-7pwq-f4pq-78gm?

No CVSS score has been assigned to GHSA-7pwq-f4pq-78gm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7pwq-f4pq-78gm?

GHSA-7pwq-f4pq-78gm affects the following packages: rustdecimal (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-7pwq-f4pq-78gm?

The records we use list no patched version of rustdecimal for GHSA-7pwq-f4pq-78gm. 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-7pwq-f4pq-78gm in my crates.io dependencies?

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

How do I mitigate GHSA-7pwq-f4pq-78gm 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-7pwq-f4pq-78gm actively exploited in the wild?

No public exploit code has been indexed for GHSA-7pwq-f4pq-78gm 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-7pwq-f4pq-78gm published, and has it been updated?

GHSA-7pwq-f4pq-78gm was published on August 11, 2022 and was last updated on November 8, 2023. 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

`rustdecimal` is a malicious crateGHSA-7pwq-f4pq-78gm

GHSA-7pwq-f4pq-78gm is a security vulnerability in rustdecimal. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asMAL-2022-1RUSTSEC-2022-0042

Published

Aug 11, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀rustdecimal

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 Rust Security Response WG and the crates.io team [were notified][1] on 2022-05-02 of the existence of the malicious crate rustdecimal, which contained malware. The crate name was intentionally similar to the name of the popular [rust_decimal][2] crate, hoping that potential victims would misspell its name (an attack called "typosquatting").

To protect the security of the ecosystem, the crates.io team permanently removed the crate from the registry as soon as it was made aware of the malware. An analysis of all the crates on crates.io was also performed, and no other crate with similar code patterns was found.

Keep in mind that the [rust_decimal][2] crate was not compromised, and it is still safe to use.

Analysis of the crate

The crate had less than 500 downloads since its first release on 2022-03-25, and no crates on the crates.io registry depended on it.

The crate contained identical source code and functionality as the legit rust_decimal crate, except for the Decimal::new function.

If your project or organization is running GitLab CI, we strongly recommend checking whether your project or one of its dependencies depended on the rustdecimal crate, starting from 2022-03-25. If you notice a dependency on that crate, you should consider your CI environment to be compromised.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`rustdecimal`	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 rustdecimal, 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 rustdecimal for GHSA-7pwq-f4pq-78gm. 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 Rust Security Response WG and the crates.io team [were notified][1] on 2022-05-02 of the existence of the malicious crate `rustdecimal`, which contained malware. The crate name was intentionally similar to the name of the popular [`rust_decimal`][2] crate, hoping that potential victims would misspell its name (an attack called "typosquatting"). To protect the security of the ecosystem, the crates.io team permanently removed the crate from the registry as soon as it was made aware of the malware. An analysis of all the crates on crates.io was also performed, and no other crate with similar

O3 Security · Impact-Aware SCA

Is GHSA-7pwq-f4pq-78gm in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works