T08 · Insecure Dependencies
- Location
README.md:35- Finding
Mutable Remote Skill Installed into an Automatically Loaded Directory
- Content
View full analysis
Vulnerability Details
File Location:
README.md:35-45
Vulnerability Type: Unpinned remote Skill installation and automatic activation
Risk Level: Mediumbash git clone https://github.com/bettermen/pc-repair.git ~/.workbuddy/skills/pc-repairThe subsequent installation instructions tell the user to restart WorkBuddy, after which the Skill is automatically loaded.
Technical Analysis
The installation command clones the mutable default branch of a remote Git repository directly into WorkBuddy's Skill-loading directory. It does not pin an immutable commit, verify a release signature or checksum, or require review of the retrieved files before activation.
Consequently, the content installed by a user can differ from the content covered by this audit. If the repository, maintainer account, or release process is compromised, an attacker could replace the reviewed Skill instructions with malicious instructions. Restarting WorkBuddy would then load the changed content automatically.
This is a supply-chain weakness rather than evidence that the currently audited repository contains a malicious payload.
Attack Path
- An attacker compromises the referenced repository, a maintainer account, or the repository's default branch.
- The attacker modifies the Skill instructions or adds harmful components.
- A user follows the documented
git clonecommand. - Git retrieves the attacker's current default-branch content directly into
~/.workbuddy/skills/pc-repair. - The user restarts WorkBuddy as instructed.
- WorkBuddy automatically loads the unreviewed, attacker-controlled Skill.
- The malicious Skill can influence agent behavior and potentially invoke any capabilities made available to the Skill by the host.
Impact Assessment
Successful exploitation could grant the attacker control over the loaded Skill's instructions and behavior. The practical scope is bounded by WorkBuddy's permissio ...[truncated 339 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace default-branch cloning with installation from an immutable, reviewed commit hash or signed release tag.
- Publish a SHA-256 checksum for each release artifact and require verification before installation.
- Sign release tags or artifacts and document signature verification.
- Download the Skill into a staging directory rather than directly into the active Skill directory.
- Require users or the host application to review and approve changed Skill instructions before activation.
- Disable automatic loading of newly installed or modified Skills until integrity and trust checks succeed.
- Document the exact audited version so users can confirm that their installed copy matches it.
