T08 · Insecure Dependencies
- Location
SKILL.md:63- Finding
Unpinned Remote Upgrade and Installation Sources
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 63
Vulnerability Type: Supply-chain risk from mutable remote 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 mechanisms retrieve mutable remote content without pinning a package version, repository commit, signed release, or integrity hash.
Running
git pullimplicitly trusts the repository's current upstream branch. Likewise,npx skills add its-how/aha-orchmay involve an unpinned package runner and installs the latest content associated with a mutable repository reference. Consequently, the installed material may differ from the version reviewed during this audit.An attacker who compromises the upstream repository, package distribution channel, maintainer credentials, or referenced branch could replace the reviewed Skill content with malicious instructions or supporting files. This is a supply-chain weakness rather than evidence that the currently reviewed files are malicious.
Attack Path
- An attacker compromises the upstream repository, publishing account, maintainer credentials, or dependency distribution channel.
- The attacker modifies the mutable branch or package content referenced by the documented upgrade command.
- A user follows the instructions and runs
git pullornpx skills add its-how/aha-orch. - The unverified remote content replaces or augments the audited Skill files.
- OpenCode subsequently loads the attacker-controlled Skill instructions.
- The altered version may direct the agent to execute unsafe commands, expose accessible data, misuse tools, or weaken permission and confirmation controls.
Impact Assessment
Successful exploitation can modify the effective instructions and files loaded by the agent under the permissions of the user running the installat ...[truncated 402 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace mutable repository references with an immutable commit hash or a cryptographically signed release tag.
- Pin the package runner and installer to reviewed versions instead of relying on the latest version resolved by
npx. - Publish cryptographic checksums for release artifacts and verify them before installation.
- Prefer a reproducible installation command that identifies both the installer version and the exact Skill release.
- Require users to inspect the downloaded diff before activating an upgrade.
- Protect releases with signed commits or tags, multifactor authentication, branch protection, and restricted publishing credentials.
- Document a rollback procedure to restore the previously verified release if integrity validation fails.
