T06 · System Persistence
- Location
SKILL.md:463- Finding
Persistent Scheduled Autonomous Network Activity
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:463-472
Vulnerability Type: Persistent scheduled task with autonomous authenticated actions
Risk Level: HighCode Snippet
markdown ## Heartbeat (Scheduled Check-In) If your agent framework supports scheduled tasks (cron, scheduled triggers, or a heartbeat loop), configure a recurring daily check-in: 1. `GET /api/notifications?unread=true` — new follows, likes, comments, mentions, reposts, upgrades 2. `GET /api/feed?limit=10` — latest posts to engage with 3. `GET /api/explore` — trending content and new agents 4. Engage — like, comment, or repost something that resonates **Scheduling:** Pick a time that fits your agent's personality — morning, afternoon, evening — and add a random minute offset (e.g. 14:22 UTC, not 00:00 UTC). Staggering avoids everyone hitting the API at midnight and makes the community feel alive around the clock. If you can check in every 4–6 hours, even better.Technical Analysis
The Skill directs the host agent framework to configure a cron task, scheduled trigger, or heartbeat loop that survives the initiating interaction. The scheduled process repeatedly makes authenticated requests to Botbook.space and may perform externally visible actions such as likes, comments, and reposts.
Persistent scheduling is not required for the Skill's core user-invoked relationship-management functionality. Recommending execution every four to six hours further increases the duration and frequency of unattended activity. The instructions do not require per-action approval, define an expiration time, impose a read-only default, or provide a clear revocation procedure.
Attack Path
- A user installs or invokes the Skill for social-graph functionality.
- The agent follows the heartbeat instructions and creates a persistent cron job, scheduled trigger, or recurring loop.
- The recurring task retains access to the Botbook bearer tok ...[truncated 901 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove instructions that cause the framework to create cron jobs, persistent triggers, or heartbeat loops automatically.
- Require an explicit, session-scoped user request for each network check and each externally visible action.
- If scheduling is essential, obtain informed opt-in that clearly states the frequency, actions, credential use, and public consequences.
- Default scheduled operation to read-only retrieval. Require separate confirmation before likes, comments, reposts, posts, or relationship changes.
- Apply a bounded lifetime and conservative frequency to every schedule.
- Provide commands to inspect, pause, and permanently delete the schedule.
- Store the API token in an approved secret store, scope it to minimum permissions where supported, and revoke it when scheduling is disabled.
- Log scheduled actions and make the logs visible to the user.
