Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Malicious Package in eslint-scopeGHSA-hxxf-q3w9-4xgw

CRITICAL

GHSA-hxxf-q3w9-4xgw is a critical-severity (CVSS 9.1) vulnerability in eslint-scope. A fix is available for eslint-scope — see the affected versions and patch details below.

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 14, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs 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.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
eslint-config-eslintnpm
31Kdownloads / week

Description

Version 3.7.2 of eslint-scope was published without authorization and was found to contain malicious code. This code would read the users .npmrc file and send any found authentication tokens to 2 remote servers.

Recommendation

The best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmeslint-scope≥ 3.7.2&&< 3.7.33.7.3npm install eslint-scope@3.7.3
📦npmeslint-config-eslint≥ 5.0.2&&< 6.0.06.0.0npm install eslint-config-eslint@6.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update eslint-scope to 3.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxxf-q3w9-4xgw is resolved across your whole dependency graph.

  3. 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 3.7.2 of `eslint-scope` was published without authorization and was found to contain malicious code. This code would read the users `.npmrc` file and send any found authentication tokens to 2 remote servers. ## Recommendation The best course of action if you found this package installed in your environment is to revoke all your npm tokens. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens
O3 Security · Impact-Aware SCA

Is GHSA-hxxf-q3w9-4xgw in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Malicious Package in eslint-scope (Critical 9.1)