How severe is GHSA-2vqq-jgxx-fxjc?

GHSA-2vqq-jgxx-fxjc has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2vqq-jgxx-fxjc?

GHSA-2vqq-jgxx-fxjc affects the following packages: motiv.scss (npm). Ecosystems affected: npm.

How do I fix GHSA-2vqq-jgxx-fxjc?

Update motiv.scss to 0.4.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vqq-jgxx-fxjc is resolved across your whole dependency graph.

How do I detect GHSA-2vqq-jgxx-fxjc in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for motiv.scss. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2vqq-jgxx-fxjc 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.

How does O3 Security protect against GHSA-2vqq-jgxx-fxjc?

O3 pinpoints whether GHSA-2vqq-jgxx-fxjc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2vqq-jgxx-fxjc actively exploited in the wild?

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

GHSA-2vqq-jgxx-fxjc was published on September 11, 2020 and was last updated on September 30, 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

GHSA-2vqq-jgxx-fxjc

CRITICAL

GHSA-2vqq-jgxx-fxjc is a critical-severity (CVSS 9.8) vulnerability in motiv.scss. O3 Security confirms whether GHSA-2vqq-jgxx-fxjc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious Package in motiv.scss

Published

Sep 11, 2020

Updated

Sep 30, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 30, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦motiv.scss

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

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

Recommendation

Remove the package from your environment and evaluate your application to determine whether or not user data was compromised.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`motiv.scss`	≥ 0.4.20&&< 0.4.21	0.4.21

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for motiv.scss. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update motiv.scss to 0.4.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vqq-jgxx-fxjc is resolved across your whole dependency graph.
Workarounds
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.
How O3 protects you
O3 pinpoints whether GHSA-2vqq-jgxx-fxjc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2vqq-jgxx-fxjc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Version 0.4.20 of `motiv.scss` contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=` ## Recommendation Remove the package from your environment and evaluate your application to determine whether or not user data was compromised.

O3 Security · Impact-Aware SCA

Is GHSA-2vqq-jgxx-fxjc in your dependencies?

O3 detects GHSA-2vqq-jgxx-fxjc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works