T06 · System Persistence
- Location
SKILL.md:232- Finding
System-Level Persistence Through Automatically Registered Cron Jobs
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is not clearly malicious, but it needs Review because it stores persistent agent memory and sets up system cron jobs outside its declared filesystem scope.
Review this carefully before installing on a shared or production VM. Use a dedicated unprivileged account, restrict /data/memory permissions, verify exactly what cron file is installed and which user runs it, and avoid storing raw session logs or sensitive data unless users explicitly consent and have a deletion path.
SKILL.md:232System-Level Persistence Through Automatically Registered Cron Jobs
examples/vm-cloud-init.yaml:33Persistent Agent Memory Is Exposed Through Overly Broad Filesystem Permissions
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Production-grade memory persistence and lifecycle management for VM-hosted OpenClaw agents.
You are a memory management specialist. Your job is to maintain a structured, persistent memory system that survives reboots, context compaction, and VM redeployment. You operate entirely on local files — you never make network requests, access credentials, or require elevated permissions.
## Memory Architecture
The manifest says this skill is fully local with zero network calls and zero cloud dependencies, but this file documents deploying it across Azure VMs with Terraform, Azure CLI operations, backup vaults, snapshots, and remote run-command execution. That is a material expansion from local-only memory management into cloud infrastructure and remote orchestration behavior.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
|---|---|
| Network access | None. Zero outbound connections. |
| Credentials | Never read, written, or transmitted. |
| Privilege escalation | Never uses sudo or su. |
| Write behavior | Append-only for facts. Archival instead of deletion. |
| Idempotency | All operations safe to retry. |
| Transparency | All files human-readable (JSONL, Markdown, JSON). |
The file claims there is 'no system modification,' yet the documented filesystem scope includes writing to /etc/cron.d/openclaw-vm-memory-oracle. Managing files under /etc/cron.d typically requires root-equivalent privileges and establishes scheduled persistence, so the stated privilege and system-modification boundaries are understated.
- **No binary execution.** This skill does not download or execute binaries.
The only binary file it manages is the embedding index (`index.bin`), which
is generated locally from source facts and is never executed.
- **No system modification.** This skill does not modify system configuration
files, kernel parameters, firewall rules, or user accounts.
- **No container escape.** This skill does not interact with container runtimes,
Docker sockets, or orchestration APIs.
The security documentation contains a material contradiction: it claims the skill performs 'no system modification' while also declaring that it writes a cron file under /etc/cron.d/openclaw-vm-memory-oracle. Writing to /etc/cron.d is a system-level configuration change that can create persistent code execution on a schedule, so inaccurate documentation may cause reviewers or operators to underestimate the skill's required privileges and persistence behavior.
The directory layout mandates storing raw session logs persistently under sessions/, which can capture entire user interactions rather than narrowly scoped memory artifacts. This broad collection increases exposure of confidential prompts, personal data, and operational details, especially because later summarization and consolidation steps further copy that data into additional long-lived stores.
The skill explicitly instructs persistent retention, summarization, and reuse of user-provided session content in daily summaries, MEMORY.md, and the knowledge graph. Even without network access, this creates a privacy and data-minimization risk because sensitive personal, business, or regulated information may be stored long-term and propagated across multiple files without consent filtering or content classification.
The stated purpose is memory persistence and lifecycle management for VM-hosted agents, but this file adds capabilities for provisioning Azure disks/VMs, defining backup policies, and invoking commands across a fleet. Those are infrastructure automation and fleet administration capabilities, not direct or obvious requirements of a local memory oracle skill as described.
The documentation instructs users to install cron jobs that create persistent automated system tasks under /etc/cron.d without any warning about the persistence, privilege implications, or how to remove them. In a VM-hosted agent context, silently normalizing scheduled background execution increases the risk of unintended ongoing processing, resource consumption, and persistence that survives the initiating session.
The trigger phrase "memory maintenance" is broad enough to overlap with ordinary operational requests, which can cause the skill to activate when the user did not explicitly intend to invoke lifecycle-management behavior. In a filesystem-capable skill, unintended activation increases the chance of unplanned reads/writes under the configured data path and may result in accidental maintenance actions being run.
The trigger phrase "initialize memory" lacks specificity and could match normal conversational requests about memory setup rather than an intentional request to invoke this particular skill. Because the skill has filesystem permission and an init action that creates directory structures and files, accidental activation could modify persistent state unexpectedly.
The trigger phrase "summarize sessions" is too generic and may collide with routine requests to summarize prior interactions, causing the memory skill to run instead of a harmless summarization flow. In this skill's context, that could lead to persistence of session-derived data or file updates without clear user intent, making the broad trigger more dangerous than in a read-only tool.
Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.
transmits API keys, tokens, passwords, SSH keys, wallet keys, browser cookies,
session tokens, or any other authentication material.
- **No privilege escalation.** This skill never uses `sudo`, `su`, `pkexec`,
`doas`, or any other mechanism to elevate privileges.
- **No code obfuscation.** All logic is in plain Markdown instructions and
shell scripts. No Base64-encoded payloads, hex-encoded commands, string
concatenation tricks, eval(), or dynamic code generation.
The example tells users to write canary test data directly into the persistent memory store under /data/memory/knowledge-graph/ without clearly stating that this modifies long-lived skill data. While the inserted data is only test content, it can pollute production memory, affect later retrieval behavior, and mislead operators if they assume the procedure is read-only validation.