How severe is GHSA-4627-w373-375v?

No CVSS score has been assigned to GHSA-4627-w373-375v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4627-w373-375v?

GHSA-4627-w373-375v affects the following packages: grunt-radical (npm). Ecosystems affected: npm.

How do I fix GHSA-4627-w373-375v?

Update grunt-radical to 0.0.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4627-w373-375v is resolved across your whole dependency graph.

How do I detect GHSA-4627-w373-375v in my npm dependencies?

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

How do I mitigate GHSA-4627-w373-375v 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-4627-w373-375v actively exploited in the wild?

No public exploit code has been indexed for GHSA-4627-w373-375v 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-4627-w373-375v published, and has it been updated?

GHSA-4627-w373-375v was published on September 11, 2020 and was last updated on August 31, 2020. 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

Malicious Package in grunt-radicalGHSA-4627-w373-375v

GHSA-4627-w373-375v is a security vulnerability in grunt-radical. A fix is available for grunt-radical — see the affected versions and patch details below.

Published

Sep 11, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · 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.

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

grunt-radicalnpm

19downloads / week

Description

Version 0.0.14 of grunt-radical 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	`grunt-radical`	≥ 0.0.14&&< 0.0.13	0.0.13`npm install grunt-radical@0.0.13`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for grunt-radical, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update grunt-radical to 0.0.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4627-w373-375v 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.0.14 of `grunt-radical` 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-4627-w373-375v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works