How severe is GHSA-2xw5-3767-qxvm?

GHSA-2xw5-3767-qxvm has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2xw5-3767-qxvm?

GHSA-2xw5-3767-qxvm affects the following packages: ng-ui-library (npm). Ecosystems affected: npm.

How do I fix GHSA-2xw5-3767-qxvm?

Update ng-ui-library to 1.0.990 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xw5-3767-qxvm is resolved across your whole dependency graph.

How do I detect GHSA-2xw5-3767-qxvm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ng-ui-library. 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-2xw5-3767-qxvm 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-2xw5-3767-qxvm?

O3 pinpoints whether GHSA-2xw5-3767-qxvm 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-2xw5-3767-qxvm actively exploited in the wild?

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

GHSA-2xw5-3767-qxvm 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-2xw5-3767-qxvm

CRITICAL

GHSA-2xw5-3767-qxvm is a critical-severity (CVSS 9.8) vulnerability in ng-ui-library. O3 Security confirms whether GHSA-2xw5-3767-qxvm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Malicious Package in ng-ui-library

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, 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

ng-ui-librarynpm

236downloads / week

Description

Version 1.0.987 of ng-ui-library 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	`ng-ui-library`	≥ 1.0.987&&< 1.0.990	1.0.990

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ng-ui-library. 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 ng-ui-library to 1.0.990 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2xw5-3767-qxvm 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-2xw5-3767-qxvm 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-2xw5-3767-qxvm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Version 1.0.987 of `ng-ui-library` 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-2xw5-3767-qxvm in your dependencies?

O3 detects GHSA-2xw5-3767-qxvm 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