T09 · Insecure Skill Coding Practices
- Location
scripts/typefully.sh:52- Finding
Schedule Parameter Allows Authenticated JSON Body Injection
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly does what it says, but it can change or publish social content and has a scheduling input flaw that merits review before use.
Install only if you are comfortable giving this skill access to manage your Typefully drafts and potentially publish or delete social content. Avoid passing schedule values copied from untrusted text, be careful with 'now' and delete-draft, and prefer a fixed version that fully validates and JSON-encodes schedule values and asks for confirmation before destructive actions.
scripts/typefully.sh:52Schedule Parameter Allows Authenticated JSON Body Injection
Referenced artifact was not completely inspected
bash scripts/typefully.sh <command> [options]
Referenced artifact was not completely inspected
bash scripts/typefully.sh <command> [options]
Referenced artifact was not completely inspected
bash scripts/typefully.sh <command> [options]
Referenced artifact was not completely inspected
bash scripts/typefully.sh <command> [options]
Referenced artifact was not completely inspected
bash scripts/typefully.sh <command> [options]
Referenced artifact was not completely inspected
bash scripts/typefully.sh <command> [options]
Referenced artifact was not completely inspected
bash scripts/typefully.sh <command> [options]
Referenced artifact was not completely inspected
bash scripts/typefully.sh <command> [options]
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
http_code=$(curl -s -w '%{http_code}' -o "$tmpfile" -X "$method" "${API_BASE}${endpoint}" \
-H "Authorization: Bearer ${API_KEY}" \
-H "Content-Type: application/json" \
"$@") || { rm -f "$tmpfile"; die "curl failed (network error)"; }
body=$(cat "$tmpfile")
rm -f "$tmpfile"
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
cmd_delete_draft() {
local draft_id="$1"
validate_draft_id "$draft_id"
api DELETE "/social-sets/${SOCIAL_SET_ID}/drafts/${draft_id}"
}
usage() {
The skill invokes shell-based tooling (bash, curl, python3) and requires sensitive credentials, but it does not declare any explicit tool restrictions such as permissions or allowed-tools. Without a scoped tool policy, an agent runtime may grant broader shell access than necessary, increasing the chance of command execution abuse, unintended side effects, or secret exposure if the skill is misused or later modified.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
#!/usr/bin/env bash
set -euo pipefail
API_BASE="https://api.typefully.com/v2"
SOCIAL_SET_ID=""
API_KEY=""
The delete-draft command issues an API DELETE request that removes a draft, but the script provides no confirmation prompt, print/log message, or inline warning near the destructive action. Although the usage text names the command, there is no explicit user disclosure that the operation is destructive or irreversible at execution time.
The create-draft command sends user-provided text to the external Typefully API via an HTTP POST, but the function does not display a notice, prompt, or comment warning that draft content will be transmitted off-system. The same script documents command usage, but it does not explicitly disclose this data-sharing behavior near execution.
The edit-draft command uploads user-supplied draft content to the external Typefully API with a PUT request, but there is no prompt, visible notice, or inline warning about transmitting that content. This is a data-affecting network operation that lacks explicit disclosure in the script itself.
No suspicious patterns detected.