T06 · System Persistence
Error
- Location
SKILL.md:169- Finding
Recurring Agent Cron Job Creates Cross-Session Persistence
- Content
View full analysis
/progress.md and features.json, and check whether any feature has remained blocked for more than three sessions. If so, output a brief report." ``` The displayed text is an English rendering of the source instructions; the cron expression and configuration fields are unchanged. ### Technical Analysis The Skill instructs the Agent to configure a recurring `agentTurn` cron job that runs every four hours. This scheduled activity can continue after the initiating Skill invocation and conversation have ended. No expiration date, maximum execution count, automatic cleanup procedure, ownership tracking, or mandatory user-confirmation step is specified. Consequently, the scheduled task may continue indefinitely and repeatedly access project files. Although the stated purpose is project monitoring rather than malicious access, the behavior matches system persistence because it installs cross-session scheduled execution. ### Attack Path 1. A user invokes the Skill for an important or long-running project. 2. The Agent follows the optional monitoring guidance and creates the specified cron job. 3. The scheduled job remains registered after the original Agent session ends. 4. Every four hours, the platform starts another Agent turn. 5. Each new turn reads `progress.md` and `features.json` and performs additional processing. 6. Without explicit expiration or removal, execution and project-file access continue indefinitely. ### Impact Assessment The scheduled task obtains the ability to initiate repeated Agent activity across sessions and read the named project-state ...[truncated 421 chars]- Remediation
View remediation