T08 · Insecure Dependencies
- Location
SKILL.md:67- Finding
Unpinned Remote Installation and Upgrade Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 67–75
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
markdown - [OMC repository](https://github.com/Yeachan-Heo/oh-my-claudecode) - OMC install command: `claude plugin marketplace add Yeachan-Heo/oh-my-claudecode` (verify against official repo before use) - [Claude Code subagents documentation](https://docs.anthropic.com/en/docs/claude-code/sub-agents) - Read `./references/capability-orchestration.md` before applying orchestration logic. It is the source of truth for orchestration steps, transparency, re-orchestration, out-of-session, cost awareness, and the 7-field discovery schema. ## Source & Upgrade - **Repository**: https://github.com/its-How/aha-orch - **Note**: This skill is part of the aha-orch multi-skill repository (contains aha-orch-xx, aha-codex-omx, aha-opencode-omo, aha-claudecode-omc). - **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 installation and upgrade procedures resolve mutable third-party content without pinning an immutable package version, repository tag, commit hash, or content digest.
In particular,
npx skills add its-how/aha-orchmay download and execute the currently publishedskillsCLI before retrieving the current repository content. The plugin marketplace command andgit pullsimilarly trust the latest upstream state. Consequently, the effective code installed by these commands can change after this Skill has been reviewed.The recommendation to verify OMC against its official repository helps prevent accidental use of an unrelated source, but it does not provide cryptographic integrity, reproducibility, or protection against compromise of the legitimate publisher account, package, marketplace entry, or repository.
Attack Path
- An attacker compromises an upstream npm publisher ...[truncated 1678 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsCLI to a reviewed, exact version instead of invoking an implicitly current release throughnpx. - Pin the Skill repository and OMC plugin to immutable release tags or, preferably, reviewed commit hashes.
- Publish and verify cryptographic checksums or signatures for downloaded artifacts before installation.
- Replace generic
git pullguidance with a reproducible upgrade procedure that fetches a specific reviewed revision. - Require users to inspect the upstream diff between the currently installed revision and the proposed revision before upgrading.
- Avoid running installation commands with administrative privileges and document the minimum required permission scope.
- Where supported, use lockfiles, package-manager integrity metadata, trusted registries, and signature verification.
- Document an explicit rollback procedure to restore the previously reviewed commit or package version if validation fails.
- Pin the
