T06 · System Persistence
Error
- Location
SKILL.md:29- Finding
Persistent Daily Policy-Monitoring Task
- Content
View full analysis
才推送（标题+摘要+URL）到主会话；NO_CHANGES 静默。 ``` The operative instructions direct the agent to use cron once per day at 09:00 in the `America/Toronto` time zone, run `scripts/policy_monitor.py`, and notify the main session when changes are detected. ### Technical Analysis The Skill declares access to the `cron` tool and instructs the agent to create recurring execution. A scheduled task survives the immediate Skill invocation and continues operating across sessions, which constitutes system persistence. The scheduled action is disclosed as a policy-monitoring feature and the audited script does not contain a malicious payload. Nevertheless, the persisted task creates a durable execution path. If the local script or Skill directory is modified later, the scheduled command may execute the modified code automatically without a new explicit user action. ### Attack Path 1. A user installs and loads the Skill. 2. The agent follows the instruction in `SKILL.md` and creates a daily cron task. 3. The cron task repeatedly invokes `scripts/policy_monitor.py`. 4. An attacker who later compromises or modifies the Skill directory replaces or alters the monitored script. 5. The next scheduled invocation runs the modified code automatically under the privileges of the account owning the cron task. ### Impact Assessment The immediate task performs outbound policy-page requests, writes monitoring state, and reports changes. Its privileges are limited to those of the user or agent environment that created the schedule. The persistence mechanism can, however, repeatedly execute future modifications to the scheduled script. This exte ...[truncated 161 chars]- Remediation
View remediation