tailwindcss-motionanimate@1.0.1
A configurable, namespaced Animate.css integration for Tailwind CSS
OpenSSF/OSV Malicious Advisory
imported 3d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18089 confirms this npm version as malicious.
Advisory
MAL-2026-18089
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in tailwindcss-motionanimate (npm)
Details
tailwindcss-motionanimate (1.0.1) is a Tailwind CSS plugin from the fake job interview campaign behind MAL-2026-17665 and MAL-2026-17666: the same Animate.css integration template, README and description, published by doublekk61 on 2026-09-28. src/motion.js:5 requires the private scoped package @jasperquinn/postcss-motion-helpers, which is not readable on the public registry and resolves only with the npm token committed in the lure repository's web/.npmrc, so the code it delivers runs when tailwind.config.js loads the plugin and the dev server starts. The published tarball contains no install scripts and no network code; the payload lives in the private dependency, which was not retrieved. Twenty-six such packages under seventeen accounts were published between 2026-07-28 and 2026-10-09.
Independent LPM AI assessment
Manual ReviewIndependent AI assessment: manual_review. LPM AI review remains unresolved.
The inspected source follows a CSS plugin path, but a required helper on that active path has unresolved registry source. This prevents a clean verdict without independently establishing malicious behavior.
Static reason
No blocking static signals were detected.
Trigger
The Tailwind plugin callback runs during Tailwind configuration processing.
Impact
The helper's behavior cannot be assessed from this snapshot, so the runtime review is incomplete.
Mechanism
The callback builds styles, and that path invokes the unavailable helper as a PostCSS plugin.
AI rationale
The inspected source follows a CSS plugin path, but a required helper on that active path has unresolved registry source. This prevents a clean verdict without independently establishing malicious behavior.
Evidence
src/motion.jspackage.jsonplugin.js
Independent scan evidence
public snapshotAI called this Manual Review at 98.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json declares @jasperquinn/postcss-motion-helpers as a required runtime dependency.
- src/motion.js imports and invokes that helper to build PostCSS output; its source was unavailable for inspection.
- plugin.js reaches the style-building path when the Tailwind plugin runs.
Evidence against
- The inspected entry point and source describe generating Tailwind CSS styles; no attack behavior was identified in those excerpts.
Behavioral surface
Filesystem
Source & flagged code
4 flagged · loading sourcepackage.jsonView file
32"@jasperquinn/postcss-motion-helpers": "^1.0.1",
"postcss-js": "^3.0.3",
"postcss-selector-parser": "^6.0.8"
},
"devDependencies": {
"eslint": "^8.5.0",
"
High
Suspicious Dependency Evidence
package.json declares @jasperquinn/postcss-motion-helpers as a required runtime dependency.
package.jsonView on unpkg · L32src/motion.jsView file
5const postcssAnimateUtils = require('@jasperquinn/postcss-motion-helpers');
function toPostcssOptions(config) {
return {
variables: {
enabled: true,
select
High
Ai Review Evidence
src/motion.js imports and invokes that helper to build PostCSS output; its source was unavailable for inspection.
src/motion.jsView on unpkg · L528const processor = postcss([postcssAnimateUtils(toPostcssOptions(config))]);
const result = processor.process('', { from: undefined }).sync();
return postcssJs.objectify(resul
High
Findings
4 High2 Low
HighSuspicious Dependency Evidencepackage.json
HighAi Review Evidencesrc/motion.js
HighAi Review Evidencesrc/motion.js
HighAi Review Evidenceplugin.js
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to tailwindcss-motionanimate@1.0.1.
See all versions of tailwindcss-motionanimate for other recorded verdicts.
- Avoid installing tailwindcss-motionanimate@1.0.1. 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.