T06 · System Persistence
- Location
dream-rem/SKILL.md:161- Finding
Recurring Cross-Session Scheduled Task Creates System Persistence
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not proven malicious, but it automatically saves, rewrites, and can delete conversation memories in the background, so it needs careful review before installation.
Install only if you want OpenClaw to keep long-term notes from your conversations. Before enabling it, disable or avoid the cron job unless you really want background consolidation, review proposed memories before saving when possible, keep backups of memory files, and avoid using it in chats that include secrets, credentials, private URLs, or sensitive account details.
dream-rem/SKILL.md:161Recurring Cross-Session Scheduled Task Creates System Persistence
extract-memories/SKILL.md:23Untrusted Conversation Content Can Be Persisted as Long-Term Agent Guidance
extract-memories/SKILL.md:42Unbounded Session Collection Can Persist Secrets and Sensitive Identifiers in Plaintext
dream-rem/SKILL.md:42Scheduled Consolidation Performs Destructive Memory Changes Without Approval or Rollback
UPDATE_FLOW.md:53Unsafe Temporary-Directory Update Procedure Can Strand Runtime Skills
The skill description states that conversation information will be written to the memory/ directory for persistent reuse, but it does not provide a clear warning or informed consent flow to the user. Because the data being extracted includes decisions, preferences, project conventions, and technical resolutions from full conversation context, this creates a meaningful privacy and data-retention risk.
The skill states that it will proactively analyze the conversation and write durable memory entries into memory/topics/ and MEMORY.md, but it does not require clear user notice or consent at the moment of retention. Persisting user decisions, preferences, constraints, and external references without transparent warning creates privacy, compliance, and trust risks, especially if the stored data later becomes accessible beyond the immediate session.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
mkdir -p ~/.openclaw/skills/
cp -r extract-memories ~/.openclaw/skills/
cp -r memory-sorting ~/.openclaw/skills/
cp -r dream-rem ~/.openclaw/skills/
The README states that the skill will automatically extract conversation-derived memories and write them into persistent topic files, but it does not prominently warn users that their chat content may be stored beyond the session. In a memory-management skill, silent persistence of user-provided information creates privacy and consent risk, especially because the trigger is automatic rather than explicitly user-confirmed each time.
The README describes deep consolidation steps that can delete outdated content and rewrite MEMORY.md, but it does not clearly warn that maintenance operations may remove or overwrite existing data. That creates integrity and recoverability risk because users may assume the tool is additive when it is actually destructive during cleanup.
The manifest description and trigger phrases are presented in Chinese, and the skill behavior implies fixed-language interaction for activation and notification without documenting any user language choice. This can violate language or locale policy when a skill enforces a specific language without opt-in or clear region-specific justification.
The skill explicitly instructs the agent to read the full conversation, extract user preferences, decisions, conventions, and solutions, and persist them to long-term storage automatically. In context, this is more dangerous because the extraction happens after every conversation by default, so sensitive personal, organizational, or project data may be retained beyond the original interaction without granular review.
The skill is configured to run automatically at the end of every conversation, which is an overly broad trigger for an operation that reads the full session and writes persistent memory. This can cause unintended invocation on sensitive chats, increasing the chance that private or irrelevant information is stored without an explicit user action at that moment.
This markdown file is written entirely in Chinese and presents the process as a mandatory standard, but it does not indicate that language is optional or limited to a China-specific audience. Under the policy criteria, forcing a specific language without user opt-in can be a natural-language policy violation.
The skill explicitly directs deletion, rewriting, and pruning of memory artifacts, including removing 'outdated' or 'incorrect' content, but it does not require a clear user-facing warning, confirmation, backup, or dry-run before destructive changes. In a memory-management skill, this is especially dangerous because normal operation can irreversibly erase user data, contradictions, or historical context based on potentially incorrect model judgments.
The core behavior of the skill is to extract conversation-derived user information and external references and save them into persistent files. Even if intended as a memory feature, automatically converting session content into durable records can capture sensitive personal or project information that was only meant for transient conversational use.
The automatic end-of-conversation and heartbeat triggers instruct the agent to read session history and persist derived content without a per-instance user request. This makes the data collection less context-aware and more likely to store unintended or sensitive material, especially because heartbeat and farewell heuristics can fire when the user did not explicitly ask to save anything.
The skill defines broad automatic end-of-conversation triggers such as common farewell phrases and also permits heartbeat-based invocation, which can cause memory extraction during ordinary chat flow rather than only after an intentional user action. Because the skill performs persistence of conversation-derived data, overbroad triggering increases the chance of collecting and storing information the user did not expect to retain.
The manifest description and main instructions are presented in Chinese, and the listed trigger phrases are also Chinese-centric except for the command name. This can impose a language requirement on users without opt-in, which matches the policy concern for forced language or locale usage.
The entire skill description, including trigger phrases and output expectations, is written only in Chinese and does not offer an alternative language or indicate that Chinese is an optional locale. This can violate language/locale policy when a skill implicitly requires a specific language without user opt-in or documented regional justification.
The skill declares an optional automatic trigger after code submission without defining narrow activation criteria, scope limits, or user confirmation. In an agent environment, broad auto-triggering can cause unintended execution on unrelated repositories or sensitive code changes, leading to surprise data access, unnecessary analysis, or workflow disruption.
All user-facing descriptive content and trigger examples in this file are presented in Chinese, with no indication that other languages are supported or that the language choice is optional. Under the policy, forcing a specific language without opt-in can be a natural-language policy violation unless clearly justified and documented.
The manifest description, headings, triggers, workflow, and command guidance are written predominantly in Chinese, with no indication that another language is supported or that the user can opt into this locale. Under the stated policy, forcing a specific language without user choice is a natural-language policy concern.