T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:11- Finding
Excessive Command Execution and File-Write Permissions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Rust guidance skill is not malicious, but it needs Review because it requests write and command-execution authority while giving inconsistent and under-scoped descriptions of file, API, network, and command behavior.
Review this before installing if you only wanted a passive Rust explainer. Do not give it administrator/root access or API keys unless the publisher clarifies exactly which commands, files, callbacks, and services are used. If installed, run it only in a sandboxed project and approve any file change or command explicitly.
SKILL.md:11Excessive Command Execution and File-Write Permissions
The skill requests exec capability even though its stated purpose is Rust pitfall guidance and code review. Unnecessary command execution materially increases the risk of arbitrary shell actions, local data exposure, and destructive side effects if the skill is triggered by adversarial or ambiguous input.
The skill defines a callback_url for asynchronous completion but later claims it does not support asynchronous processing. This inconsistency obscures network behavior and may cause users to permit outbound callbacks or expose endpoints without understanding when external requests occur.
The documentation gives conflicting statements about whether an API key is required, which can mislead users about what external services are contacted and what secrets may be needed. In a skill with read/write/exec capabilities, this ambiguity weakens trust boundaries and can cause users to expose credentials unnecessarily or misconfigure the skill.
Claiming there are no external dependencies while elsewhere describing API integration and API-related failures is materially inconsistent. This can hide the real attack surface, including outbound data transfer, service trust assumptions, and credential handling.
The manifest presents the skill as Rust guidance, but later expands its behavior into generic file handling, API integration, and command execution. This scope drift is dangerous because users may invoke a seemingly harmless educational skill while unintentionally granting it broader operational authority over the filesystem, network, and shell.
The skill advertises file writing, external API use, and command execution but does not give a clear, prominent warning about their effect on user data and systems. This creates a consent and transparency failure: users may expect passive analysis while the skill can perform active operations with side effects.
The skill's display name, summary, and description are entirely in Chinese, and the document does not indicate any language choice or opt-in for users. Under the policy, forcing a specific language without offering a locale option can be a natural-language policy violation.