T08 · Insecure Dependencies
- Location
SKILL.md:59- Finding
Installation and Execution of an Unpinned Third-Party Plugin
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 59-66
Vulnerability Type: Unpinned executable dependency
Risk Level: HighComplete Code Snippet
text ## Install ```text skill-platform plugins install @totalreclaw/totalreclaw skill-platform skills install totalreclaw skill-platform plugins enable totalreclawPublished on npm + SkillHub (
p-diogo, GitHub-verified). For a release candidate, pin with@rc; stable resolves fromlatest.text ### Technical Analysis The Skill instructs the agent to install and enable the executable `@totalreclaw/totalreclaw` package without specifying an exact version or cryptographic integrity value. The text explicitly states that stable installation resolves from the mutable `latest` release channel. Consequently, the code executed during a future installation may differ from the code that existed when this Skill was reviewed. The repository contains only `SKILL.md`; it does not include the plugin implementation needed to verify its claimed background conversation capture, relay communication, configuration updates, or process signaling. This does not establish that the current package is malicious. It creates a supply-chain trust boundary in which compromise of the publisher account, package registry, release pipeline, or mutable release tag could substitute unauthorized executable code. ### Attack Path 1. An attacker compromises the package publisher account, registry entry, or release pipeline. 2. The attacker publishes an altered package version and assigns it to the `latest` channel. 3. A user or agent follows the Skill and runs `skill-platform plugins install @totalreclaw/totalreclaw`. 4. The package manager resolves and installs the attacker-controlled release because no exact version or integrity digest is required. 5. The agent enables the plugin, allowing the substituted code to execute within the plugin or gateway environment. 6. T ...[truncated 692 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an exact, reviewed version rather than
latestor another mutable release channel. - Require and verify a cryptographic integrity digest or signed provenance attestation before installation.
- Include or vendor the reviewed plugin source so its runtime behavior can be audited with the Skill.
- Apply publisher verification, reproducible builds, lockfiles, and trusted-registry restrictions.
- Install and execute the plugin in a least-privilege sandbox with narrowly scoped filesystem and network access.
- Require explicit review before upgrades; do not automatically accept newly published versions.
- Document the exact permissions the plugin receives and provide controls to disable background capture and external transmission.
- Pin the dependency to an exact, reviewed version rather than
