T08 · Insecure Dependencies
- Location
SKILL.md:44- Finding
Unpinned Third-Party Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 44-55
Vulnerability Type: Unpinned and unverified third-party dependency installation
Risk Level: Mediumbash ### OpenCode manual installation # Clone the repository git clone https://github.com/obra/superpowers.git ~/.continue/plugins/superpowers # Or use a symbolic link ln -s /path/to/superpowers ~/.continue/plugins/ ### Codex CLI codex --install-plugin superpowersTechnical Analysis
The documented installation commands retrieve and install an executable AI-agent plugin without pinning it to a reviewed release tag or immutable commit. They also provide no checksum or signature verification procedure. The Codex installation command does not explicitly identify the expected publisher, registry, source, or version.
Consequently, the content installed by these commands can differ from the content reviewed when this Skill was published. If the upstream repository, maintainer account, plugin distribution channel, or a future release is compromised, users following the instructions could install altered plugin code, prompts, or configuration. The symbolic-link alternative can likewise expose the host agent to subsequent changes made within the linked local directory.
Attack Path
- An attacker compromises the upstream repository, a maintainer account, or the plugin distribution channel, or publishes a malicious future version.
- The attacker adds malicious scripts, prompts, configuration, or agent instructions to the mutable plugin source.
- A user follows the documented
git cloneorcodex --install-plugin superpowersinstruction without selecting a reviewed immutable version. - The host AI development tool discovers and loads the installed plugin.
- The malicious content executes or influences the agent within the permissions granted to the host tool.
Impact Assessment
The precise impact depends on the plugin-loadin ...[truncated 509 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin installation instructions to a reviewed release and immutable commit hash rather than the default branch or latest package version.
- State the authoritative repository URL, expected publisher identity, plugin registry, and exact version.
- Publish and verify a cryptographic checksum or trusted signature before enabling the plugin.
- Recommend cloning without activation, checking out the pinned commit, and reviewing its scripts, prompts, hooks, and configuration before loading it.
- Configure the host tool with least privilege and require confirmation for command execution, sensitive file access, network activity, and project modifications.
- For the symbolic-link method, warn that changes to the linked directory immediately affect the loaded plugin and recommend linking only to a read-only, reviewed checkout.
- Document a secure update process in which each new revision is reviewed and its integrity information is updated explicitly.
