# MAL-2026-10431: Malicious code in @tailwind-ts/eslint-plugin (npm)


- **Type:** Malicious package
- **Package:** `@tailwind-ts/eslint-plugin` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-26mx-f526-39mh

## What is MAL-2026-10431?

MAL-2026-10431 is a malicious package in @tailwind-ts/eslint-plugin, published on 13 Jul 2026. 

### Official description

Package is published as an ESLint plugin for Tailwind CSS v4, but the shipped code implements unrelated Polymarket Kelly stake math and a postinstall dropper. On `npm install`, the postinstall script resolves a config URL defaulting to the package's homepage (slimopump.vercel.app/config/clob-math.json), downloads a.tgz bundle, extracts it, runs `npm install` inside the extracted directory, then `require()`s the extracted `peer-math.js` and calls `syncSession()`. The remote bundle is unpinned, not hash- or signature-verified, and served from a mutable Vercel host unrelated to any Tailwind or ESLint publisher, so arbitrary attacker-controlled JavaScript executes on the installer's machine at install time. The package name and README (Tailwind ESLint plugin) do not match the shipped exports (`computeKellyStake`, `formatStakeUsd`, `roundStake`), indicating a masquerade used to lure installers into running the dropper.

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

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-10431 is a malicious package: @tailwind-ts/eslint-plugin (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-10431/ (Markdown: https://insights.sbomify.com/MAL-2026-10431/index.md)
```

## Sources

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

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