T08 · Insecure Dependencies
- Location
SKILL.md:328- Finding
Unpinned Remote Package Execution in Upgrade Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 328–329
Vulnerability Type: Unpinned third-party package and mutable upstream source
Risk Level: MediumVulnerable Code
markdown - **Repository**: https://github.com/its-How/aha-skills-finder - **Upgrade**: Run `git pull` in the skill directory, or re-run `npx skills add its-how/aha-skills-finder` to get the latest version.Technical Analysis
The documented upgrade procedure invokes
npx skillswithout pinning the package to a reviewed version or integrity hash. Depending on local npm behavior and cache state,npxmay download and execute the currently resolved package from the configured package registry.The alternative
git pullprocedure also retrieves mutable upstream content rather than a reviewed commit. Consequently, the effective code and Skill instructions installed during an upgrade can differ from those covered by this audit.This behavior is not necessary for the Skill’s normal find-stage discovery function. It is an optional maintenance path, but following it crosses a supply-chain trust boundary and can execute or install unreviewed remote content.
Attack Path
- An attacker compromises the relevant package publisher, package registry path, source repository, maintainer account, or an upstream dependency.
- The attacker publishes a malicious package version or pushes malicious content to the tracked repository branch.
- A user or Agent follows the documented
npx skills add its-how/aha-skills-finderorgit pullupgrade instruction. - The mutable remote content is downloaded without a pinned version, commit, or integrity verification.
- In the
npxpath, unreviewed package code may execute with the invoking user’s privileges. In either path, malicious Skill instructions or files may be installed and subsequently loaded.
Impact Assessment
Successful exploitation could run attacker-controlled package code with the privileges of the user ...[truncated 547 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the
skillspackage to a reviewed exact version rather than invoking an implicitly resolved latest version. - Pin the Skill source to a reviewed release tag or immutable commit hash.
- Publish and verify cryptographic checksums or signatures for release artifacts.
- Prefer downloading and inspecting the package before executing any installer.
- Use an isolated, least-privileged environment for installation and upgrade operations.
- Review repository changes before activation instead of applying an unrestricted
git pull. - Document the expected package registry and canonical package identity to reduce dependency-confusion and typosquatting exposure.
- Re-audit changed files after every upgrade and before loading the updated Skill.
- Pin the
