# GHSA-pv55-r6j3-wp94: Malicious Package in eslint-config-eslint

> A malicious npm package version steals authentication tokens from user configuration files, requiring immediate token revocation and package removal.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2020

## What is GHSA-pv55-r6j3-wp94?

GHSA-pv55-r6j3-wp94 is a vulnerability in eslint-config-eslint, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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/working_with_tokens#how-to-revoke-tokens

Users may consider downgrading to version 5.0.1

## Which versions are affected by GHSA-pv55-r6j3-wp94?

2 open source packages ship an affected version, including eslint-config-eslint.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `eslint-config-eslint` | npm | All versions | None |
| `eslint-config-eslint` | npm | All versions | None |

## How do I fix GHSA-pv55-r6j3-wp94?

No fix has been published for GHSA-pv55-r6j3-wp94 yet. Limit exposure of the affected software until one is available.

## Is GHSA-pv55-r6j3-wp94 being exploited?

There is no known exploitation of GHSA-pv55-r6j3-wp94 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-pv55-r6j3-wp94 and fix it if it is affected.

What it is: GHSA-pv55-r6j3-wp94 is a vulnerability in eslint-config-eslint, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-pv55-r6j3-wp94 in the wild and no public exploit code.

Affected packages and fixed versions:
- eslint-config-eslint (npm): affected all versions; no fix listed
- eslint-config-eslint (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-pv55-r6j3-wp94/ (Markdown: https://insights.sbomify.com/GHSA-pv55-r6j3-wp94/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-pv55-r6j3-wp94

---
From sbomify Insights: https://insights.sbomify.com/GHSA-pv55-r6j3-wp94/
Summaries are generated and may contain mistakes; the official description above is the record.