T06 · System Persistence
- Location
SKILL.md:227- Finding
Persistent Autonomous Tasks Installed Through Cron and Heartbeat Configuration
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 227-246
Vulnerability Type: Persistent scheduled agent activity
Risk Level: HighVulnerable Code:
markdown ## Automation Setup ### Cron Jobs Add to `~/.openclaw/cron/jobs.json`: ```json { "id": "bounty-search", "schedule": {"everyMs": 21600000}, "payload": { "kind": "agentTurn", "message": "Search for new bounties on GitHub and PayAClaw..." } }Heartbeat Tasks
Add to
HEARTBEAT.md:markdown ## Money Making Tasks (Every 2 hours) 1. Check PayAClaw for new tasks 2. Search GitHub bounties 3. Check PR/claim status 4. Post content if neededtext ### Technical Analysis The Skill instructs the user or agent to modify persistent OpenClaw configuration files. The cron entry schedules a new agent turn every six hours, while the heartbeat instructions request activity every two hours. These changes survive the original Skill invocation and can cause recurring network access and agent execution in future sessions. Persistence is not necessary for the Skill's core purpose as an earning guide. It is an optional automation capability and therefore should not be installed by default. The heartbeat instruction `Post content if needed` is particularly broad: it does not identify the destination, content, authorization boundaries, or conditions under which publication is permitted. If interpreted autonomously, it could result in external side effects without approval for each action. The supplied cron payload only directs searches and does not explicitly contain a backdoor or destructive command. Nevertheless, installing recurring agent turns expands the Skill's authority beyond the initiating session and violates least-privilege expectations unless the user gives explicit, informed consent. ### Attack Path 1. The user or agent loads the Skill and follows its automation instructions. 2. A recu ...[truncated 1189 chars]- Remediation
View remediation
Remediation Suggestions
- Remove cron and heartbeat modification from the default or quick-start workflow.
- Present automation as a clearly optional feature and obtain explicit informed consent before writing persistent state.
- Display the exact schedule, destinations, anticipated network requests, credentials used, and possible external side effects before installation.
- Restrict recurring jobs to read-only discovery operations.
- Require separate, per-action confirmation before submitting work, claiming bounties, creating posts, or publishing content.
- Replace
Post content if neededwith narrowly defined conditions and an approval gate. - Add resource, rate, and execution limits, along with logging and failure controls.
- Provide exact commands or instructions for disabling and removing every cron and heartbeat entry created by the Skill.
- Prefer a foreground, one-time command when persistent execution is not essential.
