T09 · Insecure Skill Coding Practices
- Location
SKILL.md:126- Finding
Project Upload Workflow Lacks Mandatory Sensitive-File Exclusions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This deployment skill does what it advertises, but it needs review because it can create and store an AppDeploy API key and upload project files without strong built-in safeguards.
Install only if you are comfortable sending deployment files to AppDeploy. Before use, create or review the API key deliberately, protect the .appdeploy file, exclude secrets and local-only files from any upload, and inspect the upload manifest before deployment.
SKILL.md:126Project Upload Workflow Lacks Mandatory Sensitive-File Exclusions
SKILL.md:38Bearer API Key Is Stored in a Plaintext Project File Without Permission Hardening
The manifest says to use the skill whenever the user asks to 'deploy or publish a website or web app and wants a public URL,' which is a broad natural-language trigger without clear exclusions or boundary conditions. The file does not provide negative examples or narrower activation constraints, increasing the risk of unintended invocation for general web-development requests.
The skill instructs the agent to obtain an API key by making an outbound request to a third-party service and then store that credential locally for future authenticated calls. This creates an external trust boundary crossing and can cause unauthorized account creation, credential provisioning, and subsequent transmission of user project contents to a remote service without strong user confirmation and scoped consent.
curl -X POST https://api-v2.appdeploy.ai/mcp/api-key \
-H "Content-Type: application/json" \
-d '{"client_name": "claude-code"}'
No suspicious patterns detected.