T06 · System Persistence
- Location
references/host-integration-playbook.md:63- Finding
Host-Level Persistence Through Scheduled Tasks
- Content
View full analysis
Vulnerability Details
File Location:
references/host-integration-playbook.md:63
Related Instruction:SKILL.md:53directs the agent to read this playbook for local deployment.
Vulnerability Type: System persistence through host automation and Windows scheduled tasks
Risk Level: HighComplete Source Snippet:
markdown - **定时任务双保险**:服务器内置定时器 + 宿主自动化(如 Windows 计划任务)各挂一份,任一失效另一份仍能兜底。English translation:
Use two safeguards for scheduled tasks: configure both a server-integrated timer and host automation such as a Windows scheduled task, so either can continue operating if the other fails.
Technical Analysis
The local-deployment playbook explicitly directs the agent to configure two persistent scheduling mechanisms, including a Windows scheduled task. A scheduled task can survive the current process, agent session, and system restart.
This exceeds the minimum privileges required for the Skill's principal declared function: generating and validating a single offline HTML workbench. Producing an offline file does not inherently require background execution or cross-session host configuration. The redundant scheduling instruction further increases persistence by arranging two independent execution paths.
The project does not include implementation code that directly creates the scheduled task; exploitation depends on an agent following the documented deployment instruction. Nevertheless, the instruction is actionable, is within a playbook the Skill directs the agent to read, and explicitly requests a recognized persistence mechanism.
Attack Path
- A user requests local deployment or a host follows the local-deployment workflow.
- Under
SKILL.md:53, the agent readsreferences/host-integration-playbook.md. - The agent follows the scheduled-task instruction at line 63.
- The agent creates both an application timer and host-level automation, such as a Windows scheduled task.
...[truncated 778 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the instruction to create Windows scheduled tasks or redundant background timers.
- Keep local deployment foreground-only and session-bound by default.
- If persistent operation is genuinely required, treat it as a separate, explicit operation requiring informed user confirmation immediately before installation.
- Display the exact executable, arguments, working directory, trigger, account, and duration before creating any persistent task.
- Apply least privilege by registering the task only for the current non-administrative user.
- Avoid elevated execution, hidden tasks, startup triggers, and automatic retries unless separately justified.
- Provide commands to inspect, disable, and permanently remove every created timer or task.
- Record an auditable receipt identifying what was installed and where, and verify cleanup when local deployment is stopped.
