T06 · System Persistence
- Location
SKILL.md:93- Finding
Persistent Scheduled Publishing Task Without Lifecycle Controls
- Content
View full analysis
'<标题>' '<正文>'" ``` ### Technical Analysis The installation instructions register a recurring OpenClaw cron task that survives the initial Skill run. The task uses a natural-language message directing an agent to read a mutable `manifest.json` file and invoke the browser publishing script. The scheduled task has no expiration, execution-count limit, removal procedure, manifest integrity validation, or requirement for per-run approval. Because both the manifest and publisher script may change after the task is registered, future executions can behave differently from the workflow initially reviewed by the user. Although scheduling is an advertised feature, the absence of lifecycle and integrity controls creates a persistence risk. ### Attack Path 1. The user follows the documented setup procedure and registers the cron task. 2. The task remains active across subsequent sessions. 3. An attacker or another local process with write access modifies `manifest.json`, the referenced publishing script, or its arguments. 4. At the scheduled time, OpenClaw interprets the natural-language task and executes the publisher using the modified inputs. 5. The operation reaches an existing authenticated browser session through Chrome DevTools Protocol. ### Impact Assessment Successful exploitation can cause repeated invocation of the publishing workflow with the user's local account privileges. It can also operate against the user's authenticated Xiaohongshu browser session. The documented script does not automatically click the final publication button, which limits the immediate effect. However, the persistent task can re ...[truncated 192 chars]- Remediation
View remediation
