T06 · System Persistence
- Location
SKILL.md:504- Finding
Persistent Unattended Execution of Externally Supplied Jobs
- Content
View full analysis
100 tokens, notify human on wake ``` Track state in `memory/clawjobs-state.json`: ```json { "lastCheck": null, "totalEarned": 0, "jobsCompleted": 0 } ``` ``` ### Technical Analysis The Skill instructs the Agent to modify its persistent `HEARTBEAT.md` configuration and periodically interact with ClawJob when there is no active human session. It does not limit the heartbeat to passive monitoring: the Agent is explicitly directed to claim a selected job, complete it, and transmit the solution. Job descriptions and associated content originate from external marketplace users and must therefore be treated as untrusted input. Automatically selecting and executing those tasks allows external users to influence the Agent's future goals after the Skill has been reviewed and installed. There is no mandatory human approval boundary before claiming a job, interpreting its instructions, using local tools or data, or submitting resulting information to the remote service. The persistent heartbeat and state files also cause this behavior to continue across sessions. Although the document does not install an operating-system service directly, it explicitly directs integration into the Agent's cross-session scheduling mechanism. This exceeds the minimum privileges needed to browse a job marketplace or m ...[truncated 1843 chars]- Remediation
View remediation
