T02 · Agent Memory Poisoning
- Location
SKILL.md:27- Finding
Persistent Poisoning of Agent Instruction and Memory Files
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This self-improvement skill is mostly disclosed, but it asks agents to persist conversation-derived content, promote it into future-session instruction files, and optionally run recurring hook scripts that are not included in the reviewed artifact.
Install only if you are comfortable with persistent learning logs and future-session instruction updates. Before use, disable or avoid the hook setup unless the referenced scripts are present and audited, require explicit approval before reading other sessions or promoting learnings, and add strict redaction rules for secrets, personal data, prompts, error output, file paths, and customer or proprietary content.
SKILL.md:27Persistent Poisoning of Agent Instruction and Memory Files
SKILL.md:89Unrestricted Cross-Session Transcript Access and Learning Propagation
SKILL.md:38Installation of Unpinned Mutable External Skill Content
SKILL.md:421Persistent Lifecycle Hooks Execute Scripts Absent from the Audited Package
The skill encourages reading other sessions' transcripts and sending learnings across sessions, which enables lateral movement of sensitive conversational data between contexts. This is especially dangerous because session boundaries often exist to limit exposure; cross-session sharing defeats that isolation if content is not strictly sanitized.
The logging templates request full context, error output, user context, and implementation details, all of which frequently include confidential content. Persisting this information in markdown records creates a durable exfiltration and accidental-disclosure surface, especially if the repository is shared or synced.
The manifest description 'use ela para essas tarefas' is vague and unconstrained, which can cause the skill to activate in many unrelated contexts. Overbroad activation increases the chance the agent applies logging and persistence behavior to ordinary conversations, including ones containing sensitive information.
The activation criteria include many common events such as user corrections, outdated knowledge, better approaches, and major tasks, which are broad enough to trigger during normal operation. In this skill's context, broad triggering is risky because activation leads directly to persistent recording of conversational content and operational details.
The skill directs the agent to log learnings, errors, and corrections to files for continuous improvement, but it provides no safeguards for secrets, personal data, or sensitive business information. Because the logging target is persistent storage and may later be promoted to memory files, sensitive user content can be retained beyond the original session.
This instruction explicitly encourages recording user corrections, requests, and operational context into persistent files and memory. That creates a direct path for user-provided content to be stored outside the original interaction boundary, increasing privacy, retention, and data-governance risk.
Creating persistent storage under ~/.openclaw/workspace/.learnings establishes session persistence that can outlive the original interaction. Persistence alone is not always unsafe, but in this skill it materially increases risk because the stored content is encouraged to include conversational and operational data.
└── FEATURE_REQUESTS.md
### Create Learning Files
```bash
mkdir -p ~/.openclaw/workspace/.learnings
The error template asks for input parameters and environment details, which commonly contain secrets, hostnames, file paths, API keys, and personal data. Without a privacy warning or sanitization requirement, the skill normalizes writing highly sensitive debugging context into durable logs.
The skill advocates broad logging and aggressive promotion into durable instruction files such as CLAUDE.md, AGENTS.md, and workspace memory. That amplifies any initial over-collection mistake by propagating sensitive or user-derived content into long-lived, widely reused prompt artifacts.
No suspicious patterns detected.