registry / Remote code execution / tailwind-plugin-kit
tailwind-plugin-kit
Tailwind CSS utilities and reusable components.
This report shows the evidence for tailwind-plugin-kit@1.3.2, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a concrete remote-code-execution loader disguised as a Tailwind plugin. Absence of an install hook limits the trigger but does not mitigate execution when the exported plugin is used.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
A consumer invokes the default-exported plugin, such as through Tailwind configuration processing.
Impact
Remote code can act with the invoking Node process's permissions.
Mechanism
remote payload execution through Function(data.credits)
Attack narrative
A project that configures and invokes this purported Tailwind plugin causes index.js to request a payload from the hard-coded IP endpoint. It reads data.credits from the JSON response, constructs a Function from it, and invokes that function with require, process, global, and Buffer. The remote operator can therefore supply arbitrary Node.js code under the consumer's privileges.
AI rationale
This is a concrete remote-code-execution loader disguised as a Tailwind plugin. Absence of an install hook limits the trigger but does not mitigate execution when the exported plugin is used.
Evidence
package.jsonindex.jsREADME.md
Network endpoints1
31.97.137.157:45000/icons/109
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The default export fetches a payload from a hard-coded IP endpoint.
- Remote JSON field data.credits is passed directly to Function and executed.
- The executed payload receives require, process, global, Buffer, and filesystem-relevant path context.
- README presents this as a Tailwind plugin, unrelated to remote code delivery.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The fetch executes only when the exported function is invoked; it is not import-time.
Behavioral surface
EvalNetwork
Source & flagged code
8 flagged · loading sourceindex.jsView file
6L7: // Create require that resolves from the project root (where package.json and node_modules are)
L8: const projectRoot = resolve(dirname(fileURLToPath(import.meta.url)), '..');
...
L90:
L91: return fetch(url, { headers: head })
L92: .then(response => {
...
L95: }
L96: return response.json();
L97: });
...
L133: exports: {},
L134: __dirname: process.cwd(),
L135: __filename: import.meta.url,
Critical
Remote Response Code Execution
Source passes code obtained from a remote response into a dynamic execution sink.
index.jsView on unpkg · L6149// Note: The code uses async/await, so we need to handle that
L150: const evalFn = new Function(
L151: 'require', 'module', 'exports', '__dirname', '__filename', 'console', 'process', 'global', 'Buffer', 'setTimeout', 'setInterval', 'clearTimeout', 'clearInterval', 'Promise',
High
•matchType = malicious_source_fingerprint_signature
signature = c06bd55d669269cb
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = prediction-trader@2.3.0
matchedPath = index.js
matchedIdentity = npm:cHJlZGljdGlvbi10cmFkZXI:2.3.0
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Findings
1 Critical7 High2 Medium1 Low
CriticalRemote Response Code Executionindex.js
HighEvalindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
HighAi Review Evidenceindex.js
HighAi Review Evidenceindex.js
HighAi Review Evidenceindex.js
HighAi Review Evidenceindex.js
HighAi Review EvidenceREADME.md
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to tailwind-plugin-kit@1.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing tailwind-plugin-kit@1.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.