T08 · Insecure Dependencies
- Location
SKILL.md:76- Finding
Unpinned Installer and Mutable Repository Used for Skill Upgrades
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 76
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
markdown - **Upgrade**: Run `git pull` in the aha-orch repo, or re-run `npx skills add its-how/aha-orch` to get the latest version.Technical Analysis
The documented upgrade process retrieves components from mutable upstream sources without pinning the installer version, repository release, or commit SHA. It also does not require checksum or signature verification.
Running
npx skills add its-how/aha-orchmay obtain and execute the currently published version of the relevant npm tooling, whilegit pullincorporates whatever content is present on the tracked upstream branch. Consequently, the effective upgrade behavior and installed Skill content can change after this version has been audited.This creates a supply-chain trust dependency on the npm publisher, package distribution infrastructure, GitHub repository, maintainer accounts, and upstream branch. A compromise of any relevant upstream publishing channel could cause a subsequent upgrade to install unreviewed or malicious content.
Attack Path
- An attacker compromises a relevant npm publisher account, package distribution channel, GitHub maintainer account, or the upstream repository.
- The attacker publishes malicious installer behavior or modifies the mutable repository branch with malicious Skill instructions or supporting content.
- A user follows the documented upgrade procedure and runs either the unpinned
npxcommand orgit pull. - The altered upstream content is downloaded without version pinning or integrity verification.
- In the
npxcase, malicious package behavior may execute during installation under the invoking user's permissions. Malicious Skill content installed from either route may subsequently influence agent sessions when loaded.
Impact Assessment
Ex ...[truncated 682 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm installer to a specifically reviewed version instead of allowing
npxto resolve the latest release. - Pin Skill installation and upgrades to a signed release tag or immutable commit SHA.
- Publish cryptographic checksums or signatures for release artifacts and verify them before installation.
- Replace unrestricted
git pullguidance with a process that fetches a specific release and displays the proposed changes for review before activation. - Use npm lockfiles or equivalent dependency-locking controls where applicable, and require integrity metadata for resolved packages.
- Run installation with the least privileges necessary in a restricted environment that does not expose credentials or sensitive workspace data.
- Require manual review of changes to Skill instructions, scripts, permissions, and external dependencies before enabling an upgraded version.
- Pin the npm installer to a specifically reviewed version instead of allowing
