Malicious code in tailwind-core (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7a6dd276f30733865042d929d52211583fa63323b5118d26e5cbe6219137f86d) Package name 'tailwind-core' impersonates the legitimate 'tailwindcss' package, using a mimicked monorepo directory ('packages/tailwind-core') and reusing tailwindlabs/tailwindcss CI badges plus links to the real tailwindcss download counts in README. The bundled library entrypoints dist/lib.mjs and dist/lib.js contain a hidden async function invoked from the Tailwind plugin factory that fires when the compiler runs during a build. After a Date.now() gate set to approximately July 2026 (timestamp 17836416e5), the code collects host reconnaissance (os.hostname, os.homedir, os.platform, os.arch, os.cpus().length, os.totalmem), derives a stable equip_id hash, and registers the host with an attacker-controlled Google Apps Script deployment via an 'addNewEquipment' call. It then enters an infinite polling loop that mints Google OAuth access tokens from a hardcoded refresh token and client_id/client_secret embedded in the bundle, retrieves base64+JSON commands from https://script.googleapis.com/v1/scripts/AKfycbyjrAVcSQB2V6XNzgYK8J0gGyx0c_ZpC0y4rFzq1IGUPu7zx7guLszZDVlcsfDzXVz3QA:run, and executes them via new Function(...), yielding arbitrary remote code execution on every installer machine running builds after the activation date. The delayed-activation timestamp gate is a time-bomb designed to evade publish-time scanning. ## Source: ghsa-malware (13f32ca9fa359af39fdc94870029079c18f805e941572fe607e6a5238b30a429) 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.
AI Analysis
Technical Summary
The tailwind-core npm package in specified versions contains embedded malicious code that compromises the host system upon installation or execution. This compromise is severe enough that all stored secrets and keys on the affected system should be rotated immediately from a different, uncompromised device. Due to the nature of the compromise, simply uninstalling the package does not ensure complete remediation, as the attacker may have established persistent control over the system.
Potential Impact
Systems with the affected tailwind-core package installed are fully compromised, potentially allowing attackers full control. All secrets and keys stored on the system are at risk and must be rotated. The compromise may persist beyond removal of the package, indicating possible additional malicious software or backdoors.
Mitigation Recommendations
Remove the tailwind-core package immediately from affected systems. Rotate all secrets and keys stored on the compromised systems using a separate, secure computer. Conduct a thorough investigation and remediation of the affected systems to identify and remove any additional malicious software or backdoors. Patch status is not applicable as this is a malicious package rather than a vulnerability with an official fix.
Malicious code in tailwind-core (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7a6dd276f30733865042d929d52211583fa63323b5118d26e5cbe6219137f86d) Package name 'tailwind-core' impersonates the legitimate 'tailwindcss' package, using a mimicked monorepo directory ('packages/tailwind-core') and reusing tailwindlabs/tailwindcss CI badges plus links to the real tailwindcss download counts in README. The bundled library entrypoints dist/lib.mjs and dist/lib.js contain a hidden async function invoked from the Tailwind plugin factory that fires when the compiler runs during a build. After a Date.now() gate set to approximately July 2026 (timestamp 17836416e5), the code collects host reconnaissance (os.hostname, os.homedir, os.platform, os.arch, os.cpus().length, os.totalmem), derives a stable equip_id hash, and registers the host with an attacker-controlled Google Apps Script deployment via an 'addNewEquipment' call. It then enters an infinite polling loop that mints Google OAuth access tokens from a hardcoded refresh token and client_id/client_secret embedded in the bundle, retrieves base64+JSON commands from https://script.googleapis.com/v1/scripts/AKfycbyjrAVcSQB2V6XNzgYK8J0gGyx0c_ZpC0y4rFzq1IGUPu7zx7guLszZDVlcsfDzXVz3QA:run, and executes them via new Function(...), yielding arbitrary remote code execution on every installer machine running builds after the activation date. The delayed-activation timestamp gate is a time-bomb designed to evade publish-time scanning. ## Source: ghsa-malware (13f32ca9fa359af39fdc94870029079c18f805e941572fe607e6a5238b30a429) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The tailwind-core npm package in specified versions contains embedded malicious code that compromises the host system upon installation or execution. This compromise is severe enough that all stored secrets and keys on the affected system should be rotated immediately from a different, uncompromised device. Due to the nature of the compromise, simply uninstalling the package does not ensure complete remediation, as the attacker may have established persistent control over the system.
Potential Impact
Systems with the affected tailwind-core package installed are fully compromised, potentially allowing attackers full control. All secrets and keys stored on the system are at risk and must be rotated. The compromise may persist beyond removal of the package, indicating possible additional malicious software or backdoors.
Mitigation Recommendations
Remove the tailwind-core package immediately from affected systems. Rotate all secrets and keys stored on the compromised systems using a separate, secure computer. Conduct a thorough investigation and remediation of the affected systems to identify and remove any additional malicious software or backdoors. Patch status is not applicable as this is a malicious package rather than a vulnerability with an official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-7026
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-m6r5-49q4-pv25"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c1968715ace4315563a
Added to database: 07/09/2026, 09:38:33 UTC
Last enriched: 07/09/2026, 09:43:43 UTC
Last updated: 07/30/2026, 05:36:54 UTC
Views: 46
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.