T06 · System Persistence
- Location
SKILL.md:69- Finding
Persistent Scheduled Polling of an External Service
- Content
View full analysis
- If new relevant services found, notify human - Track last check in memory/heartbeat-state.json ``` ## Cron Job Template For OpenClaw agents, add to your config: ```yaml cron: - name: "clawdiscover-check" schedule: kind: "every" everyMs: 21600000 # 6 hours payload: kind: "systemEvent" text: "Check ClawDiscover for new services: curl https://clawdiscover.com/api/v1/services?sort=newest&limit=10" sessionTarget: "main" ``` ``` The persistence recommendation is also corroborated by `skill.json`, lines 51-59: ```json "heartbeat": { "recommended": true, "interval": "6h", "check": "GET /api/v1/services?sort=newest&limit=10" } ``` ### Technical Analysis The skill instructs the user or hosting agent to modify persistent heartbeat configuration and install a recurring cron entry. The scheduled event survives the original skill invocation and executes every six hours in the agent's `main` session. Each execution directs the agent to contact the third-party domain `clawdiscover.com`. Although the package contains no executable scripts and does not silently install the task itself, following its documented setup establishes cross-session behavior. The external service can return changing service-discovery content after the skill has been reviewed. This creates recurring third-party network exposure and a continuing channel through which external content may influence subsequent agent activity. No evidence establishes credential theft, operating-system privilege escalation, remote code execution, or automatic execution of downloaded code. ### Attack Path 1. A user installs ...[truncated 1492 chars]- Remediation
View remediation
