T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 10–13
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
md ## Workflow 1. Inspect the existing framework, styling conventions, target background, and browser support. 2. Install `liquid-gl` with the repository's package manager. 3. Adapt `assets/react/WebGLLiquidGlass.tsx`, `webgl-liquid-glass.css`, and `liquid-gl.d.ts` for React projects. Preserve the same DOM layering in other frameworks.Technical Analysis
The workflow directs the agent to install
liquid-glwithout specifying an exact audited version, lockfile requirement, integrity hash, or trusted package source. Consequently, the package manager may resolve a release that differs from the version originally reviewed.Third-party package installation can also invoke package lifecycle scripts in the context of the developer or build environment. Although
references/tuning.mdidentifies a GitHub repository as the project source, the installation instruction does not bind the installed package to that repository, a verified registry identity, or a reviewed commit.This creates a software supply-chain risk if the package name is substituted, the publishing account or registry artifact is compromised, or a future release introduces malicious behavior.
Attack Path
- An attacker compromises the package publisher, registry artifact, or another component in the resolved dependency tree.
- The attacker publishes a malicious release under the dependency identity that the package manager will resolve.
- An agent follows the Skill workflow and installs
liquid-glwithout an exact version or integrity constraint. - The package manager retrieves the attacker-controlled release and may execute its lifecycle scripts during installation.
- Malicious code then runs in the installation or build context. If incorporated into the application bundle, it may also execute in ...[truncated 630 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the generic installation instruction with an exact, audited package version, such as
liquid-gl@X.Y.Z. - Require installation from the verified official registry identity and confirm that it corresponds to the documented upstream repository.
- Commit and enforce the package-manager lockfile, including integrity metadata, in source control.
- Use reproducible installation commands such as
npm cirather than unconstrained dependency resolution in automated environments. - Review the package and its complete transitive dependency tree before approving upgrades.
- Disable dependency lifecycle scripts where operationally feasible, or explicitly inspect required scripts before allowing them to run.
- Use automated dependency monitoring and require security review for lockfile or package-version changes.
- Replace the generic installation instruction with an exact, audited package version, such as
