T09 · Insecure Skill Coding Practices
- Location
SKILL.md:231- Finding
Authentication Token Exposed in URL Query Parameters
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent social-network integration, but it gives an agent broad shell access and directs it to perform public actions and handle tokens with weak controls.
Review before installing. This skill may create and modify public community content as an agent, sends data and tokens to clawplanet.lynto.com.cn, and relies on broad Bash access. Use it only in a sandboxed environment with no unrelated secrets, confirm each public write action manually, and avoid using a valuable identity until token recovery and token-in-URL handling are fixed.
SKILL.md:231Authentication Token Exposed in URL Query Parameters
SKILL.md:31Insecure Token Recovery Based on a Public Agent Name
SKILL.md:8Unrestricted Bash Permission Exceeds the Skill's Functional Requirements
The description presents the skill as allowing community engagement, but does not clearly warn that the agent may autonomously create public posts, comments, likes, affinity actions, and topics on the user's behalf. This weak disclosure can mislead users about the privacy and reputational consequences of enabling the skill.
The instruction that the agent should 'frequently check the timeline and post updates' is overly broad and reads like a standing behavioral directive rather than a bounded tool skill. That increases the chance of unsolicited outbound interaction, especially because later steps direct the agent to post, like, and reply on a public network.
The skill says the agent should 'frequently check the timeline and post updates' whenever interacting with the community, which creates an open-ended trigger for autonomous public actions. In a local agent with Bash(*) access, this can cause the skill to activate in broad social contexts and perform networked actions the user did not specifically authorize.
The skill directs the agent to send registration data and later authentication tokens, posts, comments, mentions queries, and other content to an external third-party domain via curl using Bash(*). In context, this is more dangerous because the workflow encourages autonomous, repeated public interactions and token handling, creating risks of data exfiltration, credential exposure, unwanted account creation, and uncontrolled outbound communications.
Example (replace the name and persona with your own):
curl -s -X POST https://clawplanet.lynto.com.cn/api/agents/register \
-H "Content-Type: application/json" \
-d '{"agent_name": "MyAgent", "persona": "A friendly AI agent"}'
The preset tags are presented entirely in Chinese, and later examples and required behaviors strongly center Chinese-language interaction without offering a language choice. A skill that effectively imposes a specific language or locale should either provide opt-in or clearly justify the constraint.
The workflow examples and reply guidance strongly steer the agent toward Chinese-language public participation without explicit user preference or consent. While not a classic exploit, this can lead to unintended public outputs, identity confusion, or reputational harm when the agent acts in a language/style the user did not request.
No suspicious patterns detected.