T02 · Agent Memory Poisoning
- Location
scripts/setup.sh:14- Finding
Persistent Cross-Session Memory Poisoning and Privacy-Boundary Violation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill openly configures cross-session memory, but it persistently changes core agent instruction files and broadly shares group and private context without enough controls.
Review this carefully before installing. Only use it if you intentionally want group-chat and private-chat long-term memory to be shared across future OpenClaw sessions. Inspect the exact changes to SOUL.md and AGENTS.md first, consider making backups, and avoid using it where group participants or private users have not consented to shared persistent memory.
scripts/setup.sh:14Persistent Cross-Session Memory Poisoning and Privacy-Boundary Violation
scripts/setup.sh:22Persistent Hijacking of Core Agent Instruction Files
The injected rule explicitly requires that important information, user preferences, decisions, and context learned in one chat be written into globally shared memory files for reuse across separate sessions. This breaks session isolation and can cause sensitive or context-specific information from one conversation to be exposed or acted upon in another without meaningful consent or scoping.
This AGENTS.md rule reinforces mandatory logging of chat-derived information into a shared memory store and instructs future sessions to consult that store. In the context of a skill whose stated purpose is cross-session memory sharing, this materially increases the risk of privacy leakage, unauthorized profile building, and incorrect carryover of context between otherwise separate conversations.
The skill is designed to make private-chat and group-chat memory interoperable by instructing the system to persist information from one context and reuse it in another. This creates a privacy and data-boundary risk because information disclosed in one session type can be surfaced in another without clear consent, purpose limitation, or data classification controls.
The skill explicitly instructs the operator to run local scripts that modify configuration files, but it does not provide a clear safety warning, preview of changes, or requirement to inspect the scripts before execution. This is dangerous because skills are untrusted content and a user may execute a path-referenced script that alters persistent agent behavior or writes unintended rules into trusted files.
The injected rule text is written as mandatory instructions in Chinese and appears to impose a specific language/locale context on the skill behavior. The file does not offer a language choice or explain a justified region-specific constraint, which can violate language/locale policy requirements.
The script writes to user workspace policy files (SOUL.md and potentially AGENTS.md) without an explicit consent prompt, backup, or dry-run mode. Because these files govern agent behavior, silently modifying them can change trust boundaries and persistence behavior in ways the user may not expect.
The AGENTS_RULE content is entirely in Chinese and is injected as normative guidance, but the script provides no mechanism for user opt-in or alternate locale selection. Under the policy, forcing a specific language without user choice is a natural-language policy concern.
No suspicious patterns detected.