tailwind-core
A utility-first CSS framework for rapidly building custom user interfaces.
This report shows the evidence for tailwind-core@4.3.2. 4 of 4 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic source inspection confirms concrete malicious behavior: host fingerprint exfiltration and remote code execution through a time-gated C2 loop. Absence of install hooks only narrows activation to runtime/build-time use; it does not make this package safe.
Decision evidence
public snapshot- dist/lib.js and dist/lib.mjs contain a time-gated async function that activates after Date.now() >= 1783641600000.
- The payload fingerprints host data via os.hostname(), homedir(), platform(), arch(), cpus().length, and totalmem().
- Fingerprint data is base64 encoded and sent as equip_desc to a Google Apps Script function named addNewEquipment.
- The code exchanges an embedded OAuth refresh token/client secret for an access token at oauth2.googleapis.com/token.
- It polls script.googleapis.com/v1/scripts/<script-id>:run every 10 seconds for base64 JSON instructions.
- Returned code is installed with new Function and then invoked, enabling remote code execution.
- package.json has no npm lifecycle hooks, so behavior is not install-time.
- The package also contains normal Tailwind-like CSS compiler code and CSS exports.
- No AI-agent control surface writes were found in inspected files.
Source & flagged code
6 flagged · loading sourceSource fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
dist/lib.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to tailwind-core@4.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing tailwind-core@4.3.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.