T06 · System Persistence
- Location
SKILL.md:76- Finding
Optional OS-Level Scheduled Tasks Create Persistent Agent Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 76–87
Vulnerability Type: OS-level recurring task registration
Risk Level: MediumVulnerable Code
bash # Linux/macOS crontab 0 12 * * * openclaw agent --message "查询 AIMPACT 早报" 0 18 * * * openclaw agent --message "查询 24H 热点新闻榜" 0 22 * * * openclaw agent --message "查询 AIMPACT 晚报"powershell # 创建每日 12:00 早报任务 schtasks /create /tn "AIMPACT早报" /tr "openclaw agent --message '查询 AIMPACT 早报'" /sc daily /st 12:00Technical Analysis
The documented commands register recurring cron jobs or a Windows Task Scheduler entry that survives the current Skill run and repeatedly launches the general-purpose
openclaw agentexecutable.This persistence is clearly presented as optional and supports the declared scheduled-news delivery feature. There is no evidence that the Skill silently installs a task or intends to create a covert backdoor. Nevertheless, OS-level persistence is not required for the Skill's core manual news-retrieval functionality and therefore exceeds the minimum privileges necessary for that core use case.
The examples also resolve
openclawthrough the scheduled task's environment rather than using a verified absolute executable path. If executable resolution or the installed binary is later compromised, the recurring task could execute attacker-controlled code. The documentation does not provide explicit consent controls, task verification, least-privilege guidance, logging, or removal instructions.Attack Path
- A user copies one of the documented cron or
schtasksconfigurations. - The operating system stores a recurring task outside the Skill directory.
- The task launches
openclaw agentevery day, including after the original session ends. - The task continues making Agent and network operations until separately disabled or removed.
- If the resolved
openclawexecutable or its runtime environment is subsequently replaced or compromised, the ...[truncated 712 chars]
- A user copies one of the documented cron or
- Remediation
View remediation
Remediation Suggestions
- Keep scheduled delivery strictly opt-in and require explicit user confirmation immediately before creating any task.
- Prefer a scoped OpenClaw-native scheduler, if available, rather than persistent OS-level task registration.
- Use a verified absolute path to the
openclawexecutable and a dedicated least-privilege account. - Restrict the scheduled operation to the news-retrieval action and avoid granting unrelated Agent tools or permissions.
- Document how to inspect and remove every example task, including the corresponding
crontabandschtasks /deleteprocedures. - Add guidance for logging, failure notification, rate limiting, and periodic review of active tasks.
- Do not create scheduled tasks automatically during installation or ordinary Skill invocation.
- Recommend manual first-run validation of the output and destination before enabling recurring delivery.
