T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:12
- Finding
- Unpinned Global Third-Party Dependency Installation<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 12-13 **Vulnerability Type**: Unpinned and globally installed third-party dependency **Risk Level**: Medium ### Vulnerable Code ```markdown - `sag` CLI (ElevenLabs TTS): `npm i -g sag` or `go install` - `ffmpeg` / `ffprobe`: `brew install ffmpeg` ``` ### Technical Analysis The installation instructions direct users to install the latest available `sag` package globally without pinning a reviewed version or verifying package integrity. The alternative `go install` instruction also omits a module path and version. A global npm installation can run package lifecycle scripts with the privileges of the installing user. Because no version or integrity digest is specified, the code installed in the future may differ from the version reviewed with this Skill. This creates supply-chain exposure if the package registry account, package release process, or dependency tree is compromised. The audit did not establish that the current `sag` package is malicious. The risk arises from trusting mutable, unverified dependency content. ### Attack Path 1. An attacker compromises the package publisher, registry account, or a transitive dependency used by `sag`. 2. The attacker publishes a malicious package release under the expected package name. 3. A user follows the Skill instructions and runs `npm i -g sag`. 4. npm retrieves the latest mutable release and executes any applicable installation lifecycle scripts. 5. Malicious code executes under the installing user's account and the package remains globally available. ### Impact Assessment Successful exploitation could execute arbitrary code with the privileges of the user performing the installation. That code could access files, environment variables, API credentials, and network resources available to that user. Global installation also increases the persistence and scope of the compromised package relative to a project-local dependency. The inst ...[truncated 243 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions - Specify the exact, verified package source and publisher. - Pin `sag` to an audited version rather than installing the latest release. - Where supported, document and verify a package integrity digest or signed release artifact. - Prefer a project-local installation over `npm i -g` to reduce system-wide exposure. - Replace the incomplete `go install` instruction with a full module path pinned to an immutable version. - Document the dependency review and update process. - Advise users not to install dependencies with elevated privileges. ]]>
