T09 · Insecure Skill Coding Practices
- Location
scripts.py:27- Finding
Configurable API Endpoint Can Expose Credentials and Search Queries
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This web-search skill does what it says, but it can send the user's search text and Turing bearer token to any configured API base without validating the destination.
Review the configured TURING_API_BASE before installing or using this skill. Use only a trusted HTTPS Turing proxy endpoint, treat search queries as data sent to that service, and prefer a narrowly scoped Turing token because the script forwards the bearer token and client/environment metadata with each search request.
scripts.py:27Configurable API Endpoint Can Expose Credentials and Search Queries
The skill documentation indicates it invokes a bundled script that performs web search through a remote proxy API, which is a network-capable action, but the skill declares no explicit tool scope such as permissions or allowed-tools. This creates a policy gap: agents or reviewers cannot reliably constrain or reason about the skill's external communication behavior, increasing the risk of unintended data egress or misuse of network access.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
"User-Agent": "openclaw-tavily-web-search",
}
response = requests.post(url, json=request_body, headers=headers, timeout=30)
response.raise_for_status()
data = response.json()
The script sends the user-provided query in an HTTP POST request and includes an API bearer token plus client/environment identifiers in headers. While the function names imply search behavior, there is no confirmation prompt or explicit user-facing disclosure near execution that input data will be sent to a remote service.
The script reads TURING_API_KEY and related values from a local configuration source and uses them to authenticate outbound requests. Although this is functionally necessary, the code provides no explicit disclosure that credentials are being read from disk and used to contact an external service.
No suspicious patterns detected.