T02 · Agent Memory Poisoning
- Location
SKILL.md:16- Finding
Unvalidated Persistent Agent Memory Modification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly a coherent OpenClaw configuration workflow, but it directs agents to write learned configuration details into persistent MEMORY.md without clear approval, redaction, or scoping.
Review this skill before installing if you do not want an agent to persist OpenClaw configuration lessons into general memory. Use it only with explicit review of any MEMORY.md entry, and avoid saving raw tokens, auth values, session identifiers, endpoints, logs, or unredacted configuration diffs.
SKILL.md:16Unvalidated Persistent Agent Memory Modification
This markdown file defines activation conditions using generic configuration-change phrases that could overlap with many ordinary requests beyond the intended OpenClaw workflow. Although line 14 narrows scope somewhat, the list does not clearly state exclusions or provide negative examples, so invocation boundaries remain ambiguous.
The skill explicitly instructs recording learned configuration values into MEMORY.md, which creates a risk of persistently storing secrets or sensitive operational details derived from authentication, model, session, or channel settings. Because the workflow covers auth-related configuration and encourages automatic learning/recording, sensitive data could be retained without user awareness or consent.
The title and the entire guide are written in Chinese, and there is no indication that other languages are supported or that the language choice is optional. Under the stated policy, forcing a specific language or locale without user opt-in is a natural-language policy concern.
This manifest describes the skill's purpose and language but does not specify any concrete trigger phrases, invocation boundaries, or exclusion conditions. For manifest files, missing specificity about when the skill should activate can lead to unintended invocation in broader contexts.
The manifest sets the skill language to "zh-CN" without indicating that users can choose another language or that the locale restriction is optional. This can violate language/locale policy when a skill forces a specific language without user opt-in or documented justification.
No suspicious patterns detected.