T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:31- Finding
Unbounded File and Skill Removal Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:31-34; duplicated inREADME.md:21-24
Vulnerability Type: T05: Unauthorized Access and Privilege Escalation
Risk Level: MediumRelevant Skill instructions, translated into English:
text ### Organize the Environment - Clean unused files and streamline workflows - Check skill matching, remove unused ones, and add needed ones - Make the entire system clean and organizedTechnical Analysis
The Skill instructs an agent to delete files and modify installed Skills without limiting these operations to a user-approved directory or explicitly identified resources. It does not require confirmation, preview proposed changes, protect sensitive paths, define how the agent should determine that an item is unused, or provide rollback and recovery controls.
These mutation instructions are not necessary for the Skill's stated purpose of documenting preferences for relaxation and enjoyable interaction. An agent could interpret the broadly worded cleanup guidance as authorization to operate on project files, configuration, or installed capabilities outside the minimum scope needed for the user's current request.
No executable code, permission-escalation implementation, persistence mechanism, or malicious payload was identified. The risk arises from unsafe agent instructions that could cause unauthorized resource modification if an agent acts on them.
Attack Path
- The Skill is loaded into an agent's active context.
- The agent interprets environmental organization as an actionable instruction.
- Without requesting explicit approval, the agent evaluates files or installed Skills and decides that some are unused.
- The agent invokes available filesystem or Skill-management tools to delete files, remove Skills, or add replacement capabilities.
- Required data or functionality is lost or altered, potentially affecting later tasks and sessions.
- Beca ...[truncated 823 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace actionable deletion language with read-only organizational recommendations.
- Require explicit user approval before every file deletion, Skill removal, Skill installation, or configuration change.
- Restrict operations to paths and resources specifically selected by the user.
- Present a complete preview of proposed changes, including affected paths and the reason each item was classified as unused.
- Define protected locations that must never be modified, including system directories, credentials, configuration, version-control metadata, and unrelated projects.
- Prefer recoverable deletion, backups, or version-controlled changes over permanent removal.
- Verify that no active workflow or dependency references a file or Skill before proposing its removal.
- Require separate confirmation for adding third-party Skills and validate their source and integrity.
- Apply the same corrected wording to the duplicated instructions in
README.md.
