# GHSA-m852-866j-69j8: Malicious Package in eslint-config-airbnb-standard

> A malicious npm package exfiltrates user credentials from .npmrc files, requiring immediate token revocation and package replacement.

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

## What is GHSA-m852-866j-69j8?

GHSA-m852-866j-69j8 is a vulnerability in eslint-config-airbnb-standard, 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 2.0.0 of `eslint-config-airbnb-standard` was published with a bundled version of `eslint-scope` that  was found to contain malicious code. This code would read the users `.npmrc` file and send it's contents 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 and use a different version of the module. You can find instructions on how to do that here. https://docs.npmjs.com/getting-started/working_with_tokens#how-to-revoke-tokens

## Which versions are affected by GHSA-m852-866j-69j8?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `eslint-config-airbnb-standard` | npm | From 2.0.0 | 2.1.0 |
| `eslint-config-airbnb-standard` | npm | From 2.0.0 | 2.1.0 |

## How do I fix GHSA-m852-866j-69j8?

Upgrade eslint-config-airbnb-standard to 2.1.0 or later.

## Is GHSA-m852-866j-69j8 being exploited?

There is no known exploitation of GHSA-m852-866j-69j8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-m852-866j-69j8 and fix it if it is affected.

What it is: GHSA-m852-866j-69j8 is a vulnerability in eslint-config-airbnb-standard, 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-m852-866j-69j8 in the wild and no public exploit code.

Affected packages and fixed versions:
- eslint-config-airbnb-standard (npm): affected from 2.0.0; fixed in 2.1.0
- eslint-config-airbnb-standard (npm): affected from 2.0.0; fixed in 2.1.0

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-m852-866j-69j8/ (Markdown: https://insights.sbomify.com/GHSA-m852-866j-69j8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-m852-866j-69j8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-m852-866j-69j8/
Summaries are generated and may contain mistakes; the official description above is the record.