How severe is GHSA-qcc9-q247-3m2m?

GHSA-qcc9-q247-3m2m has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qcc9-q247-3m2m?

GHSA-qcc9-q247-3m2m affects the following packages: js-regular (npm). Ecosystems affected: npm.

How do I fix GHSA-qcc9-q247-3m2m?

No patched version of js-regular has shipped for GHSA-qcc9-q247-3m2m 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-qcc9-q247-3m2m in my npm dependencies?

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

How do I mitigate GHSA-qcc9-q247-3m2m 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-qcc9-q247-3m2m actively exploited in the wild?

No public exploit code has been indexed for GHSA-qcc9-q247-3m2m 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-qcc9-q247-3m2m published, and has it been updated?

GHSA-qcc9-q247-3m2m was published on September 3, 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 js-regularGHSA-qcc9-q247-3m2m

CRITICAL

GHSA-qcc9-q247-3m2m is a critical-severity (CVSS 9.8) vulnerability in js-regular. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 3, 2020

Updated

Sep 30, 2021

Affected

1 pkg

Patched

None yet

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.

js-regularnpm

3downloads / week

Description

This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.

Recommendation

Remove the package from your environment. There are no indications of further compromise.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`js-regular`	≥ 0.0.0	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 js-regular, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of js-regular has shipped for GHSA-qcc9-q247-3m2m 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

This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server. ## Recommendation Remove the package from your environment. There are no indications of further compromise.

O3 Security · Impact-Aware SCA

Is GHSA-qcc9-q247-3m2m in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works