Malware in tailwindcss-merge
Malware was discovered in the npm package tailwindcss-merge, potentially compromising any system with the package installed. The advisory recommends treating affected systems as fully compromised and rotating all secrets and keys from a clean machine.
- Disclosed
- Last updated
- Blast radius
- Any system with the malicious package installed
- Ecosystems
- Attack vectors
- Affected entities
- tailwindcss-merge
A critical malware incident was identified in the npm package tailwindcss-merge. According to the GitHub Security Advisory (GHSA-m2xh-rw7p-69rx), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised machine. While the malicious package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nAffected users should assume complete system compromise and take appropriate defensive measures accordingly.
Indicators of compromise
- Packages
- tailwindcss-merge
Remediation
- Immediately rotate all secrets, API keys, and credentials from a clean, uncompromised machine
- Remove the tailwindcss-merge package from all affected systems
- Audit system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging or replacement if the system handles sensitive data
- Review and revoke any access tokens or credentials that may have been exposed
- Monitor affected systems for ongoing malicious activity
Sources
- GitHub Advisory GHSA-m2xh-rw7p-69rx · GitHub Advisory Database
Cite this entry
"Malware in tailwindcss-merge." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 11, 2026; last updated June 11, 2026. https://supplychainattack.org/incident/malware-in-tailwindcss-merge-1o5u6a
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in chain-manager
Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in @finxsecdemo/utils (npm)
The npm package @finxsecdemo/utils version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.
npmCompromised package - containedcritical
Malware in @bowozzz/baileys
The npm package @bowozzz/baileys contained malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - containedcritical
Malicious code in blots (npm)
The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.
npmCompromised package