tailwind-aspect-styles
This report shows the evidence for tailwind-aspect-styles@0.4.2, the only known version.
This package appears in our research on the fake Tailwind CSS plugins, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-16056 confirms this npm version as malicious.
Advisory
MAL-2026-16056
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in tailwind-aspect-styles (npm)
Details
The package's main module (src/index.js) performs an https.get to http://23.27.245.100/index.js over plain HTTP, writes the response to./inout.js in the consumer's working directory, and immediately require()s the written file. The fetch is unpinned, unauthenticated, and served from a bare IP over cleartext, so the operator of that endpoint controls arbitrary JavaScript executed in the Node process that loads this package. The package presents itself as the Tailwind aspect-ratio plugin, with a package.json repository field pointing to tailwindlabs/tailwindcss-aspect-ratio, while the dropper is appended after the legitimate-looking plugin export.
References
Independent scan evidence
public snapshotBehavioral surface
DynamicRequireFilesystemNetwork
UrlStrings
Source & flagged code
1 flaggedtests/test.jsView file
1const postcss = require('postcss')
L2:
Medium
Dynamic Require
Package source references dynamic require/import behavior.
tests/test.jsView on unpkg · L1Findings
2 Medium3 Low
MediumDynamic Requiretests/test.js
MediumNetwork
LowScripts Present
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to tailwind-aspect-styles@0.4.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing tailwind-aspect-styles@0.4.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.