Which versions of tailwind-merge-v2 are malicious?

Every published version of tailwind-merge-v2 on npm is considered malicious. Remove the package entirely.

How do I remediate tailwind-merge-v2 if I installed it?

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

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

Yes — tailwind-merge-v2 is associated with the GHSA-53q4-wj32-3vv9 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-merge-v2 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-merge-v2 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-merge-v2 across your stack and pipelines.

Malicious package

tailwind-merge-v2npm

Malicious code in tailwind-merge-v2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-315

Immediate action

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

npm uninstall tailwind-merge-v2

What this malware does

The package tailwind-merge-v2 was found to contain malicious code.

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

dfe4dad53bfa4f2ffe409644975e17958c4a1ab064109707aa6d944c1030b959

f95e6f494d5dae1226469ae0484efdd6da4d072c8cfb9bd7df02ff4a05a62862

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-merge-v2 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-merge-v2 across your stack and pipelines.
If you installed it — respond
Remove tailwind-merge-v2 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-merge-v2 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-merge-v2 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-merge-v2 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-53q4-wj32-3vv9

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-merge-v2-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