T09 · Insecure Skill Coding Practices
- Location
src/cli.js:92- Finding
Gateway Token Exposed Through Process Command-Line Arguments
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent X/Twitter search wrapper, but its CLI can expose a gateway token through command-line arguments and forward it to an arbitrary gateway URL.
Review before installing if you plan to use the CLI with custom gateway credentials. Prefer OpenClaw's normal OAuth setup, avoid putting tokens directly in shell commands, and do not combine --gateway-token with an untrusted --gateway-url. The core x_search use appears purpose-aligned, but the credential override path needs caution.
src/cli.js:92Gateway Token Exposed Through Process Command-Line Arguments
Without declared permissions the skill's intent is opaque and cannot be validated.
The invocation guidance is broad enough that the skill could be triggered for many loosely related requests about X/Twitter, trends, or monitoring, increasing the chance of over-invocation. In an agent environment, that can cause unintended access to external content and tool use when a narrower or more appropriate skill should have been selected, which expands attack surface and may expose the agent to untrusted content more often.
This code file parses a sensitive credential via --gateway-token and later passes it to the OpenClaw subprocess, but there is no inline warning, confirmation, or comment near the handling of this secret. Although the help text documents the flag, it does not warn users that they are supplying a sensitive token on the command line, which can have visibility/privacy implications.
Detected: suspicious.dangerous_exec