@tailwind-ts/eslint-plugin (npm) · Malicious Code
Affects @tailwind-ts/eslint-pluginSource GCVE Database
Malicious package : remove @tailwind-ts/eslint-plugin and rotate any secrets on hosts that installed it.
Data as of 14 Jul 2026, 09:27 UTC
Malicious package
Published to npm · OSV MAL-2026-10431
What to do
Remove @tailwind-ts/eslint-plugin from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@tailwind-ts/eslint-plugin | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e8feb6293e6f7cb00a6c6ab82e6d04f8eae29e846ae0abb8a1d65e2cdfbbc9c7) 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. ## Source: ghsa-malware (3bdfe62732a8b8af0a48b6b0a12daafa55c44420729ca04e9ba822699c38c830) 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.