T09 · Insecure Skill Coding Practices
- Location
SKILL.md:20- Finding
Shell Command and Argument Injection Through Unvalidated, Unquoted Parameters
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is coherent with its agent-creation purpose, but it gives new agents broad inherited access and edits core configuration with weak scoping and unsafe input handling.
Review carefully before installing. Use this only if you intentionally want new agents to inherit the main agent's auth profiles, skills, and user context, and to have broad session visibility. Prefer separate credentials per agent, validate agent IDs and Telegram IDs strictly, review the exact openclaw.json diff before applying it, and keep a known-good backup outside the automated restore path.
SKILL.md:20Shell Command and Argument Injection Through Unvalidated, Unquoted Parameters
SKILL.md:52New Agents Receive Main-Agent Credentials and Global Session Visibility
SKILL.md:121Configuration Injection Through Direct Interpolation into JSON
SKILL.md:184Wildcard-Based Backup Restoration Is Ambiguous and Unreliable
The skill handles highly sensitive operations—copying auth-profiles.json and writing Telegram bot tokens into configuration—without an upfront warning or explicit consent boundary. This increases the chance that users unknowingly duplicate credentials, broaden access between agents, or persist secrets in insecure locations, potentially enabling account takeover or lateral movement between agents.
The trigger condition is broad and example-driven, so a natural-language request that merely resembles the sample could cause the skill to run. In this skill, activation leads to filesystem writes, credential handling, config mutation, and agent provisioning, so accidental or manipulated invocation can result in unintended creation of agents and persistence of secrets.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
The manifest describes functionality that copies auth profiles and skills between agents but does not warn users that credentials or trusted capabilities may be duplicated across isolation boundaries. In a multi-agent setup, this can unintentionally broaden access, cause credential reuse, and make compromise of one agent affect others.
No suspicious patterns detected.