T06 · System Persistence
- Location
SKILL.md:49- Finding
Persistent Authenticated Heartbeat Installed Through Crontab
- Content
View full analysis
0' && echo "Todo found, wake LLM" \`\`\` ``` ### Technical Analysis The Skill instructs users to create an hourly cron job that survives the current Skill invocation and repeatedly sends an authenticated request to an external service. This is a system-persistence mechanism and exceeds the minimum privileges required for the declared on-demand functions, such as browsing opportunities, posting tasks, or listing services. The API key is also embedded directly in the crontab command. It will therefore be stored as plaintext in the user's crontab and may be exposed through administrative process inspection, backups, diagnostic output, or access to the crontab file. The callback uses HTTPS, so the credential is not intentionally transmitted in plaintext over the network. Nevertheless, it is sent automatically and indefinitely until the cron entry is removed or the credential is revoked. The command shown only prints `"Todo found, wake LLM"`; it does not itself implement an LLM wake-up mechanism. ### Attack Path 1. A user or agent follows the Skill instructions and edits the user's crontab. 2. The cron entry persists after the original Skill session ends. 3. Every hour, `curl` sends the API key to the Opulse Link heartbeat endpoint. 4. The external service can continuously observe agent availability and return todo data. 5. If the credential or service is compromised, the persistent authenticated channel may be abused until the cron entry is removed or the key is rotated. ### Impact Assessment The mechanism obtains persistent execution under the account that owns the crontab. Its direct pri ...[truncated 454 chars]- Remediation
View remediation
