T08 · Insecure Dependencies
Warning
- Location
- references/agent-platform.md:19
- Finding
- Unpinned Package Execution in Optional Agent Integration## Vulnerability Details **File Location**: `references/agent-platform.md`, lines 19–23 **Vulnerability Type**: Unpinned third-party package execution **Risk Level**: Medium **Vulnerable Code Snippet**: ```markdown The official CLI skill can also be installed for a supported agent: ```bash npx skills add godaddy/cli --skill gddy --agent <agent> ``` ``` ### Technical Analysis The documented `npx skills` command may retrieve and execute the current version of the unpinned `skills` package from the npm registry. The command does not specify an exact package version, integrity hash, lockfile, or provenance-verification procedure. Consequently, the code executed when a user follows this instruction can change after the skill has been audited. Trusting the `godaddy/cli` source repository does not independently establish the integrity of the npm launcher that downloads and installs it. This creates a supply-chain exposure if the package, a maintainer account, its dependencies, or the registry delivery path is compromised. The installation is described as optional, and the document advises users to inspect installer help before changing host configuration. These precautions reduce accidental configuration risk but do not resolve the unpinned executable dependency. ### Attack Path 1. An attacker compromises the npm package, a publishing account, or a transitive dependency associated with the `skills` launcher. 2. The attacker publishes a malicious release while retaining the expected package name. 3. A user or agent follows the documented unversioned `npx skills add ...` command. 4. `npx` resolves and downloads the mutable package version available at execution time. 5. Malicious launcher, dependency, or lifecycle code executes with the permissions of the invoking user. 6. The payload can access resources available to that user and may alter the agent’s local configuration. ### Impact Assessment Successful ex ...[truncated 562 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the launcher to an exact, reviewed package version rather than relying on the registry’s current version. 2. Record and verify the package integrity digest and npm provenance before execution. 3. Review and pin relevant transitive dependencies through an appropriate lockfile or reproducible installation mechanism. 4. Prefer a checksum-verified release artifact or an official installer whose immutable source and integrity can be independently validated. 5. Run the installer with ordinary user privileges in a constrained environment, never from an elevated shell unless strictly required. 6. Document the files and agent settings the installer is expected to modify, then require users to review those changes before approval. 7. Re-audit the pinned release before updating the documented version.