T02 Β· Agent Memory Poisoning
- Location
SKILL.md:82- Finding
Untrusted Session Content Can Poison Persistent Agent Memory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This documentation-only skill is not malicious, but it asks agents to create persistent memory and operating-rule files without enough safeguards against storing unsafe or untrusted instructions.
Install only if you intentionally want persistent agent memory. Review every proposed addition to MEMORY.md, AGENTS.md, SOUL.md, and USER.md; do not store secrets or regulated personal data; and treat remembered content as reference material that cannot override current user, developer, or system instructions.
SKILL.md:82Untrusted Session Content Can Poison Persistent Agent Memory
The invocation description includes phrases like 'agent memory', 'context window', 'agent forgets', and 'compaction', which are common topics in general AI conversations rather than narrowly scoped activation triggers. The file does not provide exclusion conditions or negative examples, so the activation boundary is unclear and could cause unintended skill invocation.
The repeated finding points to the same persistence behavior: creating a durable memory store and encouraging ongoing writes to files like MEMORY.md and daily logs. In context, the skill is specifically designed to survive compaction and preserve context, which makes persistence intentional and useful, but also amplifies privacy and data-retention risks if not bounded.
mkdir -p ~/.openclaw/workspace/memory
The repeated finding points to the same persistence behavior: creating a durable memory store and encouraging ongoing writes to files like MEMORY.md and daily logs. In context, the skill is specifically designed to survive compaction and preserve context, which makes persistence intentional and useful, but also amplifies privacy and data-retention risks if not bounded.
mkdir -p ~/.openclaw/workspace/memory
The example MEMORY.md entries are written in Chinese, while the rest of the skill is in English, and the skill does not state that this is optional or region-specific. This can be read as prescribing a language choice for stored rules without user opt-in, which conflicts with language/locale neutrality expectations.