T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:127- Finding
Broad Wildcard Indexing of Sensitive Session Transcripts
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a coherent token-optimization guide, but its optional transcript-indexing advice can make all historical OpenClaw sessions searchable without enough privacy scoping or warnings.
Review this before installing if your OpenClaw transcripts may contain secrets, personal data, proprietary code, or sensitive tool output. Avoid the wildcard transcript path unless you have reviewed and sanitized the files; prefer a small allowlist, local-only embeddings, retention limits, and rebuilding or deleting indexes when source data should no longer be searchable.
SKILL.md:127Broad Wildcard Indexing of Sensitive Session Transcripts
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
2. Check that the embedding model is downloaded
3. Ensure memory files exist and have content
### "Restart didn't clear context"
The restart clears the session history, but:
- System prompt is always loaded
The README promotes indexing old session transcripts and memory files for search without warning that those artifacts may contain secrets, personal data, credentials, or other sensitive operational context. In a memory-optimization skill, this omission is more dangerous because the feature encourages persistent aggregation and retrieval of historical data, increasing the chance of unintentional exposure or over-retention.
The skill recommends indexing ~/.openclaw/sessions/*.jsonl into searchable memory without warning that transcripts may contain sensitive prompts, secrets, personal data, or prior tool outputs. Making historical sessions broadly searchable increases the chance of unintended retrieval and disclosure of sensitive information to future agent runs or users.
The example message "Do the thing. Use message tool if human needs to know." is highly generic and overlaps with common everyday language. In a markdown skill description, this kind of unspecific invocation wording can contribute to ambiguous activation or unclear trigger scope.
No suspicious patterns detected.