Malware in tailwind-typography-stylecss
Malware discovered in the npm package tailwind-typography-stylecss. 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
- tailwind-typography-stylecss
A malware-containing version of the npm package tailwind-typography-stylecss has been identified and published to the npm registry. The advisory indicates that any computer with this package installed or running should be considered fully compromised.\n\nAccording to the GitHub Security Advisory (GHSA-p258-w6jm-c6ff), the malware grants full control of affected systems to an outside entity. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile removing the package is recommended, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise. Full system remediation and security review is necessary.
Indicators of compromise
- Packages
- tailwind-typography-stylecss
Remediation
- Immediately remove the tailwind-typography-stylecss 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 all affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
- Check npm audit logs and package.json history to identify when the malicious package was installed
Sources
- GitHub Advisory GHSA-p258-w6jm-c6ff · GitHub Advisory Database
Cite this entry
"Malware in tailwind-typography-stylecss." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 2, 2026; last updated July 2, 2026. https://supplychainattack.org/incident/malware-in-tailwind-typography-stylecss-16qp12
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 autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting