T09 · Insecure Skill Coding Practices
- Location
scripts/client.py:12- Finding
Bearer Token Disclosure Through an Unrestricted Endpoint Override
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a plausible remote-agent bridge, but it can send prompts and an auth token to externally chosen endpoints with weak transport safeguards.
Install only if you control and trust the remote endpoint. Do not use production REMOTE_AGENT_KEY with --url overrides or --insecure mode, and avoid sending secrets, regulated data, internal policy questions, or action-oriented requests unless your organization has approved that remote agent and its data handling.
scripts/client.py:12Bearer Token Disclosure Through an Unrestricted Endpoint Override
scripts/client.py:14Optional TLS Certificate and Hostname Verification Bypass
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
ctx.verify_mode = ssl.CERT_NONE
print(json.dumps({"warning": "SSL verification disabled"}, indent=2), file=sys.stderr)
with urllib.request.urlopen(req, context=ctx) as response:
response_body = response.read().decode("utf-8")
# Try to parse as JSON for pretty printing, otherwise return raw text
The skill describes delegation to external agents over HTTP but does not clearly warn users that their queries may be transmitted to a third-party or remote service. Because the examples include enterprise knowledge, financial analysis, and pipeline execution, the missing disclosure is more dangerous in context: users may provide sensitive internal data without understanding it will leave the local environment.
The skill exposes network and environment-variable capabilities but does not declare any explicit tool scope or permissions boundary. That omission makes the skill harder to review and govern, and can allow an agent to invoke external HTTP requests and use secrets without clear policy constraints or user awareness.
The usage guidance says to forward requests whenever they fall into a specialized domain, which is broad enough to capture sensitive enterprise, financial, or operational queries without meaningful limits. In practice, this can cause over-delegation of confidential prompts to a remote service, increasing the risk of data leakage, unauthorized processing, or unsafe remote actions.
No suspicious patterns detected.