T09 · Insecure Skill Coding Practices
- Location
SKILL.md:18- Finding
Azure DevOps PAT Stored in Plaintext Configuration
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent Azure DevOps helper documentation, but it tells agents to persist a personal access token in a regular config file and includes state-changing API actions without clear safety controls.
Install only if you are comfortable granting an agent Azure DevOps access. Use a least-privilege, short-lived PAT, prefer an environment variable or secret manager over persistent config storage, restrict any config file to owner-only access, and require an explicit review before creating pull requests or making other Azure DevOps changes.
SKILL.md:18Azure DevOps PAT Stored in Plaintext Configuration
SKILL.md:62Unsafe JSON Construction in Pull Request Creation Command
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
## Check before running for valid Configuration, if values missing ask the user!
**Required:**
- `AZURE_DEVOPS_PAT`: Personal Access Token
- `AZURE_DEVOPS_ORG`: Organization name
**If values are missing from `~/.openclaw/openclaw.json`, the agent should:**
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.
---
name: azure-devops
description: List Azure DevOps projects, repositories, and branches; create pull requests; manage work items; check build status. Use when working with Azure DevOps resources, checking PR status, querying project structure, or automating DevOps workflows.
metadata: {"openclaw": {"emoji": "☁️", "requires": {"bins": ["curl", "jq"], "env": ["AZURE_DEVOPS_PAT"]}, "primaryEnv": "AZURE_DEVOPS_PAT"}}
---
The skill explicitly instructs the agent to ask the user for a Personal Access Token and persist it in a local config file, but provides no warning about secure storage, file permissions, lifetime, or safer alternatives. Storing long-lived credentials on disk increases the chance of token theft through local compromise, backups, logs, or accidental file exposure.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
TITLE="PR Title"
DESCRIPTION="PR Description"
curl -s -u ":${AZURE_DEVOPS_PAT}" \
-H "Content-Type: application/json" \
-X POST \
-d '{
The pull request example performs a state-changing POST to Azure DevOps but is presented alongside read-only queries without a prominent warning or confirmation requirement. In an agent setting, this can lead to unintended remote modifications if the action is executed automatically or with ambiguous user intent.
No suspicious patterns detected.