T09 · Insecure Skill Coding Practices
- Location
README.md:24- Finding
Credential file is created without restrictive permissions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill does what it says: it sends user-requested Gotify notifications, with some credential-handling hardening users should be aware of.
Install only if you trust the Gotify server you configure. Store the config file with owner-only permissions, prefer HTTPS URLs, avoid sending secrets in notification text, and rotate the Gotify application token if it may have been exposed through logs, process inspection, or plaintext HTTP.
README.md:24Credential file is created without restrictive permissions
scripts/send.sh:69Gotify token is exposed through the curl command line and URL query string
scripts/send.sh:12Unvalidated server URL permits plaintext transmission of credentials and notification data
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
## Setup
### 1. Create an Application Token
1. Open your Gotify web UI
2. Go to **Apps** tab
The skill instructs the agent to invoke shell commands (bash scripts/send.sh ...) but does not declare any explicit tool scope such as permissions or allowed-tools. That creates an authorization gap where a host system may permit broader shell execution than users expect, increasing the chance of unintended command execution when the skill is triggered.
The description includes broad trigger phrases like 'notify me when this finishes' and 'push notification', which overlap with normal conversational requests. This can cause the skill to activate in situations the user did not specifically intend, leading to unexpected shell execution and transmission of task details to an external Gotify server.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
Create the credentials file: ~/.clawdbot/credentials/gotify/config.json
{
The workflow guidance tells the agent to automatically append && bash scripts/send.sh "Task complete" when a user says 'Notify me when this finishes'. That is an ambiguous activation rule that can silently modify user commands and initiate external network communication without a clearly bounded consent step.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
fi
# Send notification
curl -sS -X POST "$GOTIFY_URL/message?token=$GOTIFY_TOKEN" \
-H "Content-Type: application/json" \
-d "$PAYLOAD"
The README states that the skill sends push notifications via Gotify, which means message content is transmitted over the network to an external service. While this is part of the skill's purpose, the documentation does not explicitly warn users that any notification text they provide will be sent to the configured Gotify server and may appear on linked devices.
No suspicious patterns detected.