Which versions of tailwind-toolkit are malicious?

The following npm versions of tailwind-toolkit are flagged malicious: 1.3.2. Treat any of these as compromised.

How do I remediate tailwind-toolkit if I installed it?

tailwind-toolkit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tailwind-toolkit — how do I know if it already compromised me?

If tailwind-toolkit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is tailwind-toolkit part of a known attack campaign?

Yes — tailwind-toolkit is associated with the IN-MAL-2026-017750 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-toolkit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwind-toolkit (version 1.3.2).

Malicious package

tailwind-toolkitnpm

Advisory published Aug 14, 2026Updated Aug 14, 2026

tailwind-toolkit is a confirmed malicious npm package (MAL-2026-14038) that steals credentials and exfiltrates sensitive data (malicious version 1.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-toolkit (npm)

MAL-2026-14038

Immediate action

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

npm uninstall tailwind-toolkit

What this malware does

The package presents itself as a Tailwind CSS plugin, but its default export (which runs when users register it in tailwind.config) issues an HTTPS request to a hardcoded bare-IP endpoint at 31.97.137.157:45000/icons/109 and passes the response body's credits field into new Function(require, module, exports,...) for execution in the installer's Node process. The destination URL is assembled from split variables and disguised with CDN/icon vocabulary (an unused iconDomain map referencing cloudflare/fastly/akamai, a bearrtoken: "logo" header, a response field named credits), while the actual host is an unrelated bare IP on a non-standard port. The package also declares dependencies on @primno/dpapi (Windows DPAPI credential decryption), better-sqlite3/sqlite3 (browser cookie and Login Data databases), and node-machine-id, indicating the retrieved payload is a browser-credential stealer. The remote host and executed bytes are fully attacker-controlled and unrelated to the advertised Tailwind CSS purpose.

Malicious versions

1 flagged

1.3.2

Indicators of compromise (SHA-256)

afeb355b3088d1c03dbbb5a60c1afea5afbe3a384f50417ae6cfa7340d8c072d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tailwind-toolkit (version 1.3.2).
If you installed it — respond
tailwind-toolkit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tailwind-toolkit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-017750

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-toolkit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database