# MAL-2026-5466: Malicious code in getd-eslint-rules (npm)


- **Type:** Malicious package
- **Package:** `getd-eslint-rules` (npm)
- **Published:** 9 Jun 2026
- **Also known as:** GHSA-jqwv-7cxv-rhvm

## What is MAL-2026-5466?

MAL-2026-5466 is a malicious package in getd-eslint-rules, published on 9 Jun 2026. 

### Official description

On `npm install`, postinstall.js collects host identifiers (os.hostname, os.userInfo username, os.platform, current working directory, CI environment variable, and package name/version) and sends them as query-string parameters in an HTTPS GET to a hardcoded webhook.site collector URL (postinstall.js line 18: `https://webhook.site/18dc4281-d366-438a-9186-76fbcd56ade5?pkg=...&host=...&user=...&platform=...&cwd=...&ci=...`). The fetch fires automatically on install and errors are silently swallowed. The package self-describes as a 'defensive typo-squat' research artifact, but installer-side identifiers are exfiltrated to a third-party request collector without consent regardless of stated intent. The package name pattern targets users who mistype an ESLint rules package, increasing the chance of unintended installation.

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-5466?

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-5466 is a malicious package: getd-eslint-rules (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-5466/ (Markdown: https://insights.sbomify.com/MAL-2026-5466/index.md)
```

## Sources

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

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