T08 · Insecure Dependencies
- Location
SKILL.md:12- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:12; related usage atassets/react/SDFLiquidGlass.tsx:2
Vulnerability Type: Unpinned third-party dependency
Risk Level: MediumVulnerable code snippets:
SKILL.md:12markdown 2. Install `vaso` with the repository's package manager.assets/react/SDFLiquidGlass.tsx:2tsx import { Vaso } from 'vaso'Technical Analysis
The skill instructs the agent to install
vasowithout specifying an audited version, immutable source commit, lockfile requirement, or integrity hash. The bundled React component subsequently imports and executes the installed package.Package managers may therefore resolve whichever package version currently satisfies the unconstrained request. If the package, a transitive dependency, or its publishing account is compromised, an attacker could introduce malicious lifecycle scripts or browser-side code after this skill has been reviewed. The linked upstream repository in
references/tuning.mddocuments the intended project but does not ensure that installation resolves to a verified artifact from that repository.This is a supply-chain weakness rather than evidence that the current
vasopackage is malicious.Attack Path
- An attacker compromises the package publisher, a transitive dependency, or the relevant registry artifact.
- The attacker publishes a malicious version under the expected package name.
- A user invokes the skill and follows its instruction to install
vasowithout an exact version or verified integrity value. - The package manager resolves the attacker-controlled release.
- Malicious code executes through an installation lifecycle script or when the React application imports and runs the package.
Impact Assessment
Install-time code could execute with the permissions of the user or automation account running the package manager. Depending on that environment, the affecte ...[truncated 517 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the unconstrained installation instruction with an exact, reviewed package version, such as
vaso@<audited-version>. - Commit and enforce the package manager's lockfile so direct and transitive dependency versions remain reproducible.
- Verify registry provenance, package ownership, and integrity metadata before installation.
- Pin to an immutable, reviewed commit when sourcing directly from a repository.
- Run dependency installation with lifecycle scripts disabled where compatible with the package and build process.
- Use automated dependency scanning, but require review and testing before accepting version updates.
- Install dependencies under a least-privileged account and avoid exposing unnecessary credentials to package-manager processes.
- Replace the unconstrained installation instruction with an exact, reviewed package version, such as
