T06 · System Persistence
- Location
SKILL.md:27- Finding
Persistent Daily Update Task Executes Without Fresh User Approval
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 27-35
Vulnerability Type: Persistent scheduled task
Risk Level: HighVulnerable Code
bash SkillHub cron add \ --name "Daily Auto-Update" \ --cron "0 4 * * *" \ --tz "America/Los_Angeles" \ --session isolated \ --wake now \ --deliver \ --message "Run daily auto-updates: check for SkillHub updates and update all skills. Report what was updated."Technical Analysis
The Skill instructs the user or Agent to create a daily cron task that persists after the initial Skill interaction. The task wakes an isolated Agent session and directs it to update SkillHub and every installed Skill without obtaining fresh approval for the specific changes.
This creates a persistent execution mechanism tied to mutable upstream content. Although the scheduled task is consistent with the stated auto-update purpose and is disclosed to the user, it remains a cross-session persistence mechanism. Its security properties depend on how the scheduled Agent interprets the message and on the trustworthiness of every upstream update available at execution time.
Attack Path
- A user asks the Agent to configure the auto-updater.
- The Agent runs the documented
SkillHub cron addcommand. - The cron entry persists beyond the current session and wakes an isolated session every day.
- An upstream SkillHub or Skill release is compromised or maliciously modified.
- The scheduled session retrieves and applies the affected update without presenting its contents for review or requesting fresh approval.
- The updated component subsequently operates with the permissions available to the Gateway or scheduled Agent process.
Impact Assessment
The recurring task can cause future software and Skill changes to be applied under the account running SkillHub. The accessible scope can include installed Skill directories, SkillHub configuration, an ...[truncated 415 chars]
- Remediation
View remediation
Remediation Suggestions
- Do not create a recurring scheduled task by default.
- Require explicit, informed confirmation before installing the cron entry.
- Prefer a scheduled dry run or update notification that reports available versions without installing them.
- Require fresh user approval for the exact set of packages and Skills before each update is applied.
- Run the scheduled check with a dedicated, least-privileged account that cannot modify unrelated files or system-wide packages.
- Display the complete generated cron configuration, execution identity, update commands, and affected directories before installation.
- Provide a direct rollback procedure in addition to the documented cron removal command.
- Record update activity in an auditable log and alert the user when the scheduled task changes or fails.
