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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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

Malicious Package in motiv.scssGHSA-2vqq-jgxx-fxjc

CRITICAL

GHSA-2vqq-jgxx-fxjc is a critical-severity (CVSS 9.8) vulnerability in motiv.scss. A fix is available for motiv.scss — see the affected versions and patch details below.

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

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

motiv.scssnpm

97downloads / week

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`npm install motiv.scss@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works