T06 · System Persistence
- Location
references/setup-guide.md:41- Finding
Optional LaunchAgent and Cron Configuration Creates Cross-Session Scheduled Execution
- Content
View full analysis
Label com.isp-throttle-detective ProgramArguments /bin/sh -c python3 /path/to/skills/isp-throttle-detective/scripts/speedtest.py | python3 /path/to/skills/isp-throttle-detective/scripts/log_result.py StartInterval 1800 RunAtLoad ``` ```bash launchctl load ~/Library/LaunchAgents/com.isp-throttle-detective.plist ``` ```bash crontab -e # Add: */30 * * * * python3 /path/to/skills/isp-throttle-detective/scripts/speedtest.py | python3 /path/to/skills/isp-throttle-detective/scripts/log_result.py >> ~/.isp-throttle-detective/cron.log 2>&1 ``` ### Technical Analysis The setup guide instructs the user to register either a macOS LaunchAgent or a Linux cron job that executes the Skill every 30 minutes. These registrations survive the initiating shell and continue operating across user sessions, meeting the definition of a system-persistence mechanism. Periodic execution is functionally relevant because detecting time-dependent bandwidth patterns requires multiple measurements. The mechanism is also openly documented and is not installed automatically by the Python scripts. Nevertheless, it exceeds the privileges and duration required for a single speed test or report-generation operation. Once configured, every scheduled run performs multiple external downloads, uploads approximately 5 MB to Cloudflare, and appends results to p ...[truncated 2111 chars]- Remediation
View remediation
