Which versions of @tailwind-ts/eslint-plugin are malicious?

The following npm versions of @tailwind-ts/eslint-plugin are flagged malicious: 0.3.0. Treat any of these as compromised.

How do I remediate @tailwind-ts/eslint-plugin if I installed it?

Remove @tailwind-ts/eslint-plugin from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @tailwind-ts/eslint-plugin — how do I know if it already compromised me?

If @tailwind-ts/eslint-plugin was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @tailwind-ts/eslint-plugin part of a known attack campaign?

Yes — @tailwind-ts/eslint-plugin is associated with the IN-MAL-2026-010204 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @tailwind-ts/eslint-plugin across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @tailwind-ts/eslint-plugin (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @tailwind-ts/eslint-plugin across your stack and pipelines.

Malicious package

@tailwind-ts/eslint-pluginnpm

Malicious code in @tailwind-ts/eslint-plugin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10431

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @tailwind-ts/eslint-plugin

What this malware does

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.

Malicious versions

1 flagged

0.3.0

Indicators of compromise (SHA-256)

e8feb6293e6f7cb00a6c6ab82e6d04f8eae29e846ae0abb8a1d65e2cdfbbc9c7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @tailwind-ts/eslint-plugin (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @tailwind-ts/eslint-plugin across your stack and pipelines.
If you installed it — respond
Remove @tailwind-ts/eslint-plugin from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @tailwind-ts/eslint-plugin was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @tailwind-ts/eslint-plugin before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @tailwind-ts/eslint-plugin on npm has been identified as a malicious package (version 0.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010204

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @tailwind-ts/eslint-plugin-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring