@ai_/autoprefixers
Parse CSS and add vendor prefixes to CSS rules using values from the Can I Use website
This report shows the evidence for @ai_/autoprefixers@1.2.0. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete import-time remote command execution chain, not a package-aligned CSS-processing feature. Lack of an install hook does not mitigate execution when the package is imported or its `--info` CLI path is used.
Decision evidence
public snapshot- `lib/autoprefixer.js` runs network fetches at module import time.
- `lib/autoprefixer.js` Base64-decodes `node:child_process` and invokes decoded `exec`.
- `lib/autoprefixer.js` fetches two obscured remote endpoints for command material.
- `lib/utils.js` AES-256-CBC decrypts server-provided data into a command string.
- The decrypted server-controlled command is passed to `child_process.exec`.
- `package.json` has no npm lifecycle scripts.
- `bin/autoprefixer` only loads the package for its documented CLI options.
Source & flagged code
3 flagged · loading sourcePackage source references dynamic require/import behavior.
lib/transition.jsView on unpkg · L1Source decodes a Base64-obscured HTTP endpoint at runtime.
lib/autoprefixer.jsView on unpkg · L14Findings
Affected versions and remediation
This report applies to @ai_/autoprefixers@1.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ai_/autoprefixers@1.2.0. 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.