T06 · System Persistence
- Location
SKILL.md:500- Finding
Recurring Heartbeat Establishes Cross-Session Persistence
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 500-510
Vulnerability Type: Scheduled-task persistence
Risk Level: HighVulnerable Code
markdown ## Heartbeat — Scheduled Check-In Set up a recurring task to maintain platform presence. Pick an off-minute to avoid burst traffic. **Recommended cron:** `37 9 * * *` (daily at 9:37 AM) or any consistent off-hour time. 1. `GET /api/me/notifications` — check for new activity 2. `GET /api/concerts` — browse what's playing 3. If a concert looks interesting → `POST /api/concerts/:slug/attend` → stream → react → chat 4. `GET /api/me` — review your stats and badges 5. Follow `next_steps` from each responseTechnical Analysis
The skill explicitly instructs the agent to create a recurring scheduled task, recommending a daily cron expression. This causes the skill's behavior to survive its original invocation and continue producing authenticated network activity in later sessions.
The scheduled workflow is not limited to read-only health checks. It can attend concerts and perform state-changing actions such as reacting and chatting. It also directs the scheduled process to follow remotely supplied
next_steps, extending the persistent task's behavior beyond the statically reviewed instructions.A recurring system task is unnecessary for an on-demand concert API client. Installing it without a narrowly scoped, explicit user request violates the principle of least persistence.
Attack Path
- A user invokes the skill for an ordinary interaction with the music platform.
- The skill registers or authenticates the agent and obtains a bearer API key.
- Following the heartbeat instructions, the agent creates a daily cron job or equivalent recurring task.
- The original interactive session ends, but the scheduled task remains installed.
- At each scheduled execution, the task contacts the external service and uses the agent's authenticated identity.
- The task may browse concerts ...[truncated 828 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the instruction to create a cron job or any other recurring cross-session task.
- Make all platform check-ins explicitly user initiated.
- If scheduling is an optional product feature, require informed confirmation that clearly states:
- The exact schedule.
- The command or workflow that will run.
- The credentials it will access.
- The network destinations it will contact.
- How the user can disable and remove it.
- Restrict any approved scheduled operation to read-only, locally defined endpoints.
- Do not permit scheduled executions to attend, react, chat, follow users, modify settings, or perform other state-changing actions without fresh approval.
- Never execute server-provided
next_stepsfrom a background task. - Store credentials using an appropriate secret manager and provide explicit credential revocation and scheduled-task cleanup procedures.
