T06 · System Persistence
- Location
scripts/setup_cron.sh:39- Finding
Persistent Daily Agent Task Is Installed by the Setup Script
- Content
View full analysis
/dev/null || { echo " ⚠ Could not create hermes cron job" echo " You can manually add it later:" echo " hermes cron create '0 3 * * *' --name session-archivist-daily --prompt 'python3 $ARCHIVER'" } ``` ### Technical Analysis The setup script registers a daily Hermes cron task that persists after the setup process and across Agent sessions. The scheduled task instructs an Agent to execute `session_archiver.py`, which scans, reads, archives, optionally transmits, and rewrites qualifying session files. The installation is documented and therefore is not hidden. Nevertheless, it creates a persistent execution mechanism with broad access to the invoking user's Hermes session data. The setup process does not request a separate confirmation immediately before persistence is installed, display a removal command, or constrain the scheduled operation to a narrowly scoped non-Agent executable action. ### Attack Path 1. A user follows the documented installation instructions and runs `scripts/setup_cron.sh`. 2. The script creates the `session-archivist-daily` recurring Hermes task. 3. At 03:00 each day, Hermes receives a prompt instructing it to execute the archiver. 4. The archiver scans all qualifying sessions under the configured Hermes home directory. 5. Sessions may be archived, sent to Hindsight, and destructively trimmed without per-run user approval. ### Impact Assessment The task runs with the permissions of the Hermes user. It does not directly escalate operating-system privileges, but it persistsently exercises that user's access to Hermes session files and configured mem ...[truncated 277 chars]- Remediation
View remediation
