T06 · System Persistence
- Location
SKILL.md:100- Finding
Persistent Scheduled Agent Execution
- Content
View full analysis
" ``` ### Technical Analysis The documented command registers a recurring OpenClaw cron task that survives the initial skill run and invokes the agent every day. Each scheduled invocation can conduct web searches, modify local state and source files, generate content, and publish that content to an external messaging channel. This constitutes system persistence because execution continues across sessions until the cron entry is explicitly removed. The behavior is openly documented and requires the user to run the setup command; the audit found no evidence of covert installation or an undisclosed backdoor. Nevertheless, the scheduled job creates an unattended execution path with network, filesystem, and external-publication effects. The use of an isolated session limits session-level carryover but does not eliminate the persistence itself or the risks associated with processing changing web content without interactive review. ### Attack Path 1. A user follows the installation instructions and runs the supplied `openclaw cron add` command. 2. OpenClaw registers the `clawvicular-daily` recurring task. 3. At 10:00 AM Pacific Time each day, the task starts an isolated agent session without requiring fresh user approval. 4. The skill performs web searches against external, dynamically changing content. 5. It updates local state and the persistent source archive. 6. It publishes generated output to the configured Telegram or other messaging destination. 7. This process repeats until ...[truncated 963 chars]- Remediation
View remediation
