# MAL-2026-13980: Malicious code in eslint-generate-release (npm)


- **Type:** Malicious package
- **Package:** `eslint-generate-release` (npm)
- **Published:** 13 Aug 2026
- **Also known as:** GHSA-3pw3-hc35-j73p

## What is MAL-2026-13980?

MAL-2026-13980 is a malicious package in eslint-generate-release, published on 13 Aug 2026. 

### Official description

eslint-generate-release@99.9.1 is a hollow package whose index.js exports an empty object and whose only effect on install is dependency resolution. package.json declares a runtime dependency `ltidisafe` whose version specifier is not an npm-registry version but a direct HTTPS tarball URL: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.3.tgz. On `npm install`, npm fetches and installs that off-registry tarball into node_modules, introducing code that never passed through the npm registry. The package name mimics the ESLint ecosystem and the 99.9.1 version is a version-squat pattern; combined with the empty main entry, the package functions purely as a smuggling wrapper for the URL-referenced payload.

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

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

## Sources

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

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