Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious Package in eslint-config-eslint

GHSA-pv55-r6j3-wp94

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm eslint-config-eslint

    Affected
    >= 5.0.2, <= 5.0.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Version 5.0.2 of eslint-config-eslint 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 a remote server. 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/workingwithtokens#how-to-revoke-tokens Users may consider downgrading to version 5.0.1

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-pv55-r6j3-wp94

  2. Revision 1 · created ·

    Published from osv record GHSA-pv55-r6j3-wp94

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-pv55-r6j3-wp94

Advisory: Malicious Package in eslint-config-eslint
IDs: GHSA-pv55-r6j3-wp94
Record: https://patchnext.com/advisories/ghsa-pv55-r6j3-wp94 (revision 2, source checked 26 Oct 2026, 12:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm eslint-config-eslint: affected >= 5.0.2, <= 5.0.2

## Suggested inspection (read-only)
- `npm ls eslint-config-eslint --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on eslint-config-eslint.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pv55-r6j3-wp94 (OSV record GHSA-pv55-r6j3-wp94 lists affected ranges: npm eslint-config-eslint >=5.0.2 <=5.0.2)
- Verified: https://github.com/advisories/GHSA-pv55-r6j3-wp94 (GitHub-reviewed advisory GHSA-pv55-r6j3-wp94 lists affected ranges: npm eslint-config-eslint >=5.0.2 <=5.0.2)

Commands are suggestions: review each one before running it.

Loading voting…