How severe is GHSA-m25q-fwg4-9v2p?

GHSA-m25q-fwg4-9v2p has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-m25q-fwg4-9v2p?

GHSA-m25q-fwg4-9v2p affects the following packages: awesome_react_utility (npm). Ecosystems affected: npm.

How do I fix GHSA-m25q-fwg4-9v2p?

No patched version of awesome_react_utility has shipped for GHSA-m25q-fwg4-9v2p 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-m25q-fwg4-9v2p in my npm dependencies?

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

How do I mitigate GHSA-m25q-fwg4-9v2p 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-m25q-fwg4-9v2p actively exploited in the wild?

No public exploit code has been indexed for GHSA-m25q-fwg4-9v2p 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-m25q-fwg4-9v2p published, and has it been updated?

GHSA-m25q-fwg4-9v2p was published on September 1, 2020 and was last updated on September 24, 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 awesome_react_utilityGHSA-m25q-fwg4-9v2p

CRITICAL

GHSA-m25q-fwg4-9v2p is a critical-severity (CVSS 9.8) vulnerability in awesome_react_utility. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 1, 2020

Updated

Sep 24, 2021

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 24, 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, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

awesome_react_utilitynpm

5downloads / week

Description

Version 1.0.2 of awesome_react_utility contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=

Recommendation

If version 1.0.2 of this module is found installed you will want to replace it with a version before or after 1.0.2. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`awesome_react_utility`	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 awesome_react_utility, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of awesome_react_utility has shipped for GHSA-m25q-fwg4-9v2p 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

Version 1.0.2 of `awesome_react_utility` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=` ## Recommendation If version 1.0.2 of this module is found installed you will want to replace it with a version before or after 1.0.2. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.

O3 Security · Impact-Aware SCA

Is GHSA-m25q-fwg4-9v2p in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works