How severe is GHSA-mvch-rh6h-2m47?

GHSA-mvch-rh6h-2m47 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mvch-rh6h-2m47?

GHSA-mvch-rh6h-2m47 affects the following packages: equest (npm). Ecosystems affected: npm.

How do I fix GHSA-mvch-rh6h-2m47?

No patched version of equest has shipped for GHSA-mvch-rh6h-2m47 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-mvch-rh6h-2m47 in my npm dependencies?

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

How do I mitigate GHSA-mvch-rh6h-2m47 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-mvch-rh6h-2m47 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mvch-rh6h-2m47 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-mvch-rh6h-2m47 published, and has it been updated?

GHSA-mvch-rh6h-2m47 was published on September 11, 2020 and was last updated on October 1, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

Malicious Package in equestGHSA-mvch-rh6h-2m47

CRITICAL

GHSA-mvch-rh6h-2m47 is a critical-severity (CVSS 9.8) vulnerability in equest. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 11, 2020

Updated

Oct 1, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Oct 1, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

equestnpm

4downloads / week

Description

All versions of equest typosquatted a popular package of similar name and tracked users who had installed the incorrect package. The package uploaded information to a remote server including: name of the downloaded package, name of the intended package, the Node version and whether the process was running as sudo. There is no further compromise.

Recommendation

Remove the package from your dependencies and always ensure package names are typed correctly upon installation.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`equest`	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 equest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of equest has shipped for GHSA-mvch-rh6h-2m47 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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

All versions of `equest` typosquatted a popular package of similar name and tracked users who had installed the incorrect package. The package uploaded information to a remote server including: name of the downloaded package, name of the intended package, the Node version and whether the process was running as sudo. There is no further compromise. ## Recommendation Remove the package from your dependencies and always ensure package names are typed correctly upon installation.

O3 Security · Impact-Aware SCA

Is GHSA-mvch-rh6h-2m47 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works