T06 · System Persistence
- Location
SKILL.md:54- Finding
Recurring Cron Job Creates Persistent Unattended Execution
- Content
View full analysis
/dev/null; echo "5 15 * * 1-5 cd ~/.openclaw/workspace && python3 skills/aky-select/scripts/aky_select.py >> skills/aky-select/logs/aky_\$(date +\%Y\%m\%d).log 2>&1") | crontab - ``` ### Technical Analysis The documented command modifies the current user's crontab and configures the Skill to execute automatically at 15:05 every weekday. The scheduled task survives the current Skill invocation and future login sessions. Persistent scheduling is optional convenience functionality rather than a prerequisite for the declared stock-screening operation. The core operation can be performed through the documented one-time invocation. Therefore, modifying persistent user configuration exceeds the minimum access necessary to perform an individual screening. The cron entry executes a script through a path inside the user's writable workspace. If that script, its directory, the Python interpreter resolution, or an imported dependency is subsequently modified, the altered code will run unattended at the next scheduled interval. The command also appends an identical entry every time it is executed, so repeated setup can create duplicate scheduled executions, duplicated network traffic, and additional log growth. The persistence is disclosed rather than hidden, and it is only installed if the user follows the command. Nevertheless, the resulting execution remains persistent and carries the authority of the user who owns the crontab. ### Attack Path 1. The user follows the scheduling instructions in `SKILL.md`. 2. The command appends the recurring entry to the user's crontab. 3. The task remains active after the current terminal or agent session ends. 4. The referenced script or one of its imported dependencies is later replaced, com ...[truncated 1186 chars]- Remediation
View remediation
