T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:4- Finding
Mutable Remote Executable Is Downloaded and Trusted Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Taskleef skill is coherent, but it needs Review because it installs an unpinned external CLI that will use the user's API key and it documents destructive task commands without confirmation guidance.
Install only if you trust the upstream Taskleef CLI source and are comfortable giving it your Taskleef API key. Prefer a pinned release or verified checksum before execution, avoid running setup as root, and require explicit confirmation with exact IDs before delete, project delete, or board clear actions.
SKILL.md:4Mutable Remote Executable Is Downloaded and Trusted Without Integrity Verification
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
brew install jq
# Ubuntu/Debian
sudo apt-get install jq
# CentOS/RHEL
sudo yum install jq
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
brew install jq
# Ubuntu/Debian
sudo apt-get install jq
# CentOS/RHEL
sudo yum install jq
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.
cd taskleef/taskleef-cli chmod +x todo
export PATH="$PATH:/path/to/taskleef/taskleef-cli"
The README explicitly advertises destructive capabilities like completing and deleting todos but does not warn users that the skill can modify or permanently remove Taskleef data. In an agentic context, missing disclosure increases the risk of users invoking the skill without understanding it performs write operations, which can lead to unintended data loss or workflow disruption.
The skill documents direct deletion commands for todos without any warning, confirmation guidance, or safer alternatives. In an agent setting, users may issue ambiguous requests and the agent could choose a destructive action that permanently removes task data, increasing the risk of unintended data loss.
Project deletion is a higher-risk destructive operation because it may remove organizational structures and potentially associated task relationships. Without a warning about data loss or a recommendation to confirm intent, an agent could delete the wrong project based on partial title/ID matching, causing broader accidental disruption.
Clearing a board column is a bulk destructive action that can affect multiple cards at once, making mistakes more damaging than single-item commands. Combined with flexible identifier matching, this increases the chance that an agent or user clears the wrong column and causes significant unintended task loss or workflow disruption.
No suspicious patterns detected.