T01 · Skill Instruction Hijacking
- Location
SKILL.md:34- Finding
Automatic Persistent Capture of Ordinary User Messages
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:34
Vulnerability Type:T01: Skill Instruction Hijacking
Risk Level: HighVulnerable Instruction
markdown Any user message, regardless of whether it has a clear purpose, should be treated as worth recording.Technical Analysis
The skill instructs the hosting agent to treat ordinary user messages as content that should be recorded, even when the user has not explicitly requested note creation. This changes the agent's default behavior from responding to conversation to persistently capturing it.
The surrounding operational instructions specify that note content is appended to
~/.openclaw/workspace/notes-data/notes.jsonand that original statements should be preserved. When the host follows these instructions, casual messages can therefore become persistent records without informed, per-message consent.The Python module does not itself implement automatic capture; the behavior is delegated to the agent through
SKILL.md. Nevertheless, instruction-driven behavior is part of the skill's effective execution model.Attack Path
- The daily-notes skill is loaded into an agent session.
- A user sends an ordinary message that does not explicitly request note creation.
- The quoted instruction causes the agent to classify the message as worth recording.
- Following the documented record operation, the agent stores the message and inferred metadata in
~/.openclaw/workspace/notes-data/notes.json. - The captured content persists across sessions until it is deleted or archived.
This path does not require code execution, elevated system privileges, or network access; it relies on the host agent obeying the skill instructions.
Impact Assessment
The affected scope is the user's local notes workspace and any conversation content available to the agent while the skill is active. Potentially sensitive thoughts, health details, financial ...[truncated 376 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the instruction that treats every user message as recordable by default.
- Require an explicit note-taking command or an affirmative confirmation before each persistent write.
- Clearly disclose the destination file and the categories of metadata that will be stored.
- Add a sensitivity check for health, financial, credential, identity, and other private information, and require additional confirmation before storing such content.
- Provide configurable retention limits and straightforward review, export, and deletion controls.
- Default to no persistence when user intent is ambiguous.
- Require confirmation before permanent deletion of notes or associated images.
