T06 · System Persistence
- Location
SKILL.md:302- Finding
Persistent Scheduled Task Registration Creates a Durable Execution Channel
- Content
View full analysis
~/Library/LaunchAgents/com.user.cleanup-downloads.plist << 'EOF' Label com.user.cleanup-downloads ProgramArguments /bin/bash /Users/me/scripts/cleanup-downloads.sh StartCalendarInterval Hour 9 Minute 0 EOF # Load it launchctl load ~/Library/LaunchAgents/com.user.cleanup-downloads.plist # Add to crontab (crontab -l 2>/dev/null; echo "0 9 * * * /home/user/scripts/cleanup.sh") | crontab - ``` Additional persistent registration examples include: ```bash systemctl --user daemon-reload systemctl --user enable --now cleanup.timer ``` ```powershell schtasks /create /tn "DailyCleanup" /tr "powershell.exe -File C:\scripts\cleanup.ps1" /sc daily /st 09:00 ``` ### Technical Analysis These commands register jobs that remain active after the current Skill invocation and execute scripts in later sessions. Recurring automation is part of the declared Skill functionality, and the Skill separately classifies scheduled-task modification as an operation requiring explicit confirmation. Therefore, the behavior is not hidden or inherently unrelated to the Skill. Nevertheless, the examples establish persistent execution without showing safeguards such as restrictive permissions on the referen ...[truncated 1333 chars]- Remediation
View remediation
