Malware in tailwindcss-effector
Malware was discovered in the npm package tailwindcss-effector. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- tailwindcss-effector
A malicious package named tailwindcss-effector was published to npm and contains malware. Any computer that has this package installed or running should be considered fully compromised.\n\nThe malware grants full control of the affected system to an outside entity. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected computer.\n\nWhile the package should be removed, removal may not eliminate all malicious software that resulted from the installation, as the attacker may have established persistent access or deployed additional payloads.\n\nThis incident was disclosed via GitHub Advisory GHSA-5xpc-q26w-px3q on 2026-07-07.
Indicators of compromise
- Packages
- tailwindcss-effector
Remediation
- Immediately identify all systems with tailwindcss-effector installed
- Isolate affected systems from the network if possible
- Remove the tailwindcss-effector package from all systems
- Rotate all secrets, API keys, and credentials from a clean, unaffected computer
- Perform a full security audit and malware scan of affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
- Monitor for any signs of persistent malware or backdoors
Sources
- GitHub Advisory GHSA-5xpc-q26w-px3q · GitHub Advisory Database
Cite this entry
"Malware in tailwindcss-effector." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-tailwindcss-effector-1iqx37
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package