T01 · Skill Instruction Hijacking
- Location
SKILL.md:57- Finding
Untrusted Local Override File Can Hijack Audit Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This workspace-audit skill is not obviously malicious, but it can automatically scan and change or remove persistent workspace memory without clear approval or rollback controls.
Install only if you are comfortable with a skill that may read broad workspace and memory context and make persistent cleanup changes. Prefer running it manually in report-only mode, reviewing proposed deletions, moves, renames, and MEMORY.md edits before applying them, and keeping backups or version control for the workspace.
SKILL.md:57Untrusted Local Override File Can Hijack Audit Instructions
SKILL.md:38Automatic Destructive Workspace Cleanup Lacks Approval and Recovery Controls
SKILL.md:19Audit Procedure Performs Overly Broad Sensitive-Context Reconnaissance
The skill explicitly instructs the agent to merge, deduplicate, prune, archive, and rename files, including deleting entries deemed 'no longer useful,' but provides no explicit safety warning, approval gate, backup requirement, or dry-run mode. In an automated nightly or cron-triggered context, these destructive actions could silently cause data loss, corrupt user memory organization, or remove important information based on heuristic judgments.
The trigger language is extremely broad ('when the user asks to audit, clean up, or check workspace health') for a skill that performs wide filesystem scans and may modify, archive, rename, or delete files. This increases the chance of unintended invocation in ambiguous conversations, causing the agent to run destructive maintenance actions without sufficiently explicit user intent.
The file explicitly instructs the agent to remove sections from MEMORY.md, move files to memory/archive/, and update references, but it does not require an explicit user-facing warning or confirmation about the risk of altering or effectively deleting stored memory content. In a workspace-audit skill that may run automatically on a nightly cron job, these retention changes can silently hide, relocate, or remove important context and create data-loss or integrity issues if the classification is wrong.