postcss-initialize-provider
PostCSS plugin to fallback initial keyword.
This report shows the evidence for postcss-initialize-provider@3.0.4, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe payload executes on package import and has a concrete network-to-eval-to-detached-process chain. The absence of lifecycle hooks does not mitigate import-time arbitrary code execution.
Decision evidence
public snapshot- index.js contains a large obfuscated import-time IIFE unrelated to PostCSS.
- The IIFE imports HTTP/S, zlib, URL, child_process, and reads ETH_RPC_URL.
- It fetches/decrypts remote content then passes it to eval and a detached node -e child process.
- package.json has no npm lifecycle hook, but importing the main entry triggers the payload.
- The visible PostCSS fallback logic and lib/rules-fabric.js are package-aligned.
- No install/preinstall/postinstall script is declared.
Source & flagged code
6 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
index.jsView on unpkg · L7index.js contains a large obfuscated import-time IIFE unrelated to PostCSS.
index.jsView on unpkg · L8The IIFE imports HTTP/S, zlib, URL, child_process, and reads ETH_RPC_URL.
index.jsView on unpkg · L8Findings
Affected versions and remediation
This report applies to postcss-initialize-provider@3.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing postcss-initialize-provider@3.0.4. 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.