# MAL-2026-13977: Malicious code in cspell-esm (npm)


- **Type:** Malicious package
- **Package:** `cspell-esm` (npm)
- **Published:** 13 Aug 2026
- **Also known as:** GHSA-97mm-cxmj-h672

## What is MAL-2026-13977?

MAL-2026-13977 is a malicious package in cspell-esm, published on 13 Aug 2026. 

### Official description

Package name resembles the widely-used 'cspell' library but its main entry (index.js) exports an empty object and provides no functionality. Its package.json pins its sole dependency 'ltidisafe' to a raw HTTPS URL on a Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.7.tgz) rather than a registry-published, version-pinned artifact. On `npm install`, npm fetches this tarball from the author-controlled bucket and installs it into the dependency tree, executing any of its lifecycle scripts and main-module code on the installer's machine. The combination of a lookalike name, an empty implementation, and an off-registry dependency source is the dropper-lure shape: the lure package itself is inert, and installer-side code execution is delivered through the smuggled dependency.

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

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-13977 is a malicious package: cspell-esm (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-13977/ (Markdown: https://insights.sbomify.com/MAL-2026-13977/index.md)
```

## Sources

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

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