Which versions of tailwind-configuration are malicious?

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

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

Remove tailwind-configuration 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-configuration — how do I know if it already compromised me?

If tailwind-configuration 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-configuration part of a known attack campaign?

Yes — tailwind-configuration is associated with the RLMA-2026-02046 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-configuration across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwind-configuration (version 1.0.1).

Malicious package

tailwind-configurationnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

tailwind-configuration is a confirmed malicious npm package (MAL-2026-2803) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-configuration (npm)

MAL-2026-2803

Immediate action

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

npm uninstall tailwind-configuration

What this malware does

The package tailwind-configuration was found to contain malicious code.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

12c20b1e64e9ad2b7e8b576753836742bcfaa39234608a02cf2106c06061d7f7

60061f038f742f65f6876c278646b1b91d880677e6ba9dff2c87ea021f5b6aa9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tailwind-configuration (version 1.0.1).
If you installed it — respond
Remove tailwind-configuration 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-configuration 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-configuration on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02046

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks tailwind-configuration-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

Explore

All malware advisories How O3 detects malware Vulnerability database