tailwindcss-hook-forms@0.5.2
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-19145 confirms this npm version as malicious.
OpenSSF/OSV advisory MAL-2026-19145 confirms this npm version as malicious.
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.
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
scripts/release-notes.js2 highscripts/release-channel.js1 highpackage.json2 highsrc/index.js1 highscripts/release-notes.js2 findingsscripts/release-channel.js1 findingpackage.json2 findingssrc/index.js1 findingSource file is highly similar to a previously finalized malicious package; route for source-aware review.
scripts/release-notes.jsView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
scripts/release-notes.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
scripts/release-channel.jsView on unpkgThe package entry point is src/index.js, so its top-level code runs when the package is imported.
package.jsonView on unpkg · L2The package is a Tailwind forms plugin, but the purpose of the automatically compiled payload is not established from the readable source.
package.jsonView on unpkg · L23The entry point contains encoded text, decodes a constructor name, and passes a second decoded string to that constructor for dynamic compilation.
src/index.jsView on unpkg · L55This report applies to tailwindcss-hook-forms@0.5.2.
See all versions of tailwindcss-hook-forms for other recorded verdicts.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.