This report shows the evidence for tailwindcss-hook-forms@0.5.2. 1 of 2 known versions is blocked or flagged.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-19145 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-19145 confirms this npm version as malicious.
Advisory
MAL-2026-19145
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in tailwindcss-hook-forms (npm)
Details
The package impersonates @tailwindcss/forms: name, repository (tailwindlabs/tailwindcss-forms), author (@tailwindcss), README, CHANGELOG, and HTML are copied from the legitimate plugin, with a demo link to tailwindcss-hook-forms.vercel.app. src/index.js prepends a hand-rolled string-permutation decoder (spin() with magic constants NX/SX, splitLane/peel wrappers) that resolves the Function constructor via peel.constructor and immediately invokes a function compiled from a ~15KB opaque, obfuscated string literal, passing the host require into it. This fires whenever any consumer imports the package, running attacker-controlled code in the installer's Node.js process with full access to require, process, filesystem, and network. The subsequent code replicates the public API of @tailwindcss/forms as cover. The obfuscator scheme does not exist in the legitimate plugin and its only purpose is to conceal the executable body from review.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The package entry point automatically compiles a large encoded payload during import, and its purpose cannot be established from the readable source. No install hook or concrete malicious action was identified, so classify this as suspicious rather than malicious.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Importing the package through its main entry point, src/index.js.
Impact
The concealed code can execute during import; its behavior and effects are not established, so this presents an unresolved risk.
Mechanism
The entry point decodes strings, obtains a constructor through a computed property, and passes decoded content to it for compilation.
Evidence
src/index.js
Independent scan evidence
public snapshot
AI called this Suspicious at 87.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
The package entry point is src/index.js, so its top-level code runs when the package is imported.
The entry point contains encoded text, decodes a constructor name, and passes a second decoded string to that constructor for dynamic compilation.
The package is a Tailwind forms plugin, but the purpose of the automatically compiled payload is not established from the readable source.
Evidence against
The manifest has no install lifecycle scripts.
The readable release scripts only derive release notes and a release channel.
The remaining visible entry-point code defines ordinary Tailwind form styles.
Behavioral surface
SourceEnvironment variables · Filesystem
Supply chainHigh entropy strings · URL strings
ManifestNo manifest risk signals triggered.
Scanned 4 files · 25.8 KB of source
1 external domain referenced
www.w3.org
Findings
6 high · 1 medium · 4 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Forge('z', peel("ei t dt = gm0e; lo ).D( llpbllk e.htu e/i oeq i a =sPue
Affected versions and remediation
This report applies to tailwindcss-hook-forms@0.5.2.
The versions list below shows the verdict for each recorded version.
Avoid installing tailwindcss-hook-forms@0.5.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.