# MAL-2026-17157: Malicious code in eslint-config-compact-base (npm)


- **Type:** Malicious package
- **Package:** `eslint-config-compact-base` (npm)
- **Published:** 24 Sep 2026
- **Also known as:** GHSA-gx7g-jjf6-c7jg

## What is MAL-2026-17157?

MAL-2026-17157 is a malicious package in eslint-config-compact-base, published on 24 Sep 2026. 

### Official description

index.js executes on module load and collects host reconnaissance data — os.platform(), os.hostname(), os.userInfo().username, architecture, Node version, current working directory — together with CI-context environment variables including CI, RUNNER_NAME, and GITHUB_REPOSITORY. The collected values are serialized as query-string parameters and sent via https.get to the hardcoded endpoint https://cbrsuo9293.execute-api.us-east-1.amazonaws.com/c. The behavior fires unconditionally on require(), so any build, install, or CI job that pulls in this ESLint config beacons its host identity and repository name to the attacker-controlled AWS API Gateway. This network activity has no relationship to the package's advertised purpose as an ESLint configuration.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-17157?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17157 is a malicious package: eslint-config-compact-base (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17157/ (Markdown: https://insights.sbomify.com/MAL-2026-17157/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17157

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17157/
Summaries are generated and may contain mistakes; the official description above is the record.