T09 · Insecure Skill Coding Practices
Warning
- Location
scripts/validate.py:151- Finding
Symbolic-Link Path Escape in GetX Page Generator
- Content
View full analysis
- Remediation
View remediation
Security audit
flutter-schema
Security checks for vulnerabilities and agentic risk
Overview
This Flutter scaffolding skill is mostly coherent, but its generator can be tricked into writing new files outside the intended project folder through symlinks.
Review before installing if you plan to use the scaffold generator. The architecture guidance itself is low risk, but run scripts/validate.py only in trusted Flutter repositories and avoid target directories containing symlinks until the path containment check is hardened with realpath/lstat-style validation and no-follow file creation.
Vulnerability Patterns
- Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
- Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
- Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)
Vulnerability Patterns
- MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)
Undeclared Tool Scope
Medium
- Category
- MCP Least Privilege
- Confidence
- 70% confidence
- Finding
Without declared permissions the skill's intent is opaque and cannot be validated.
- Content
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 91% confidence
- Finding
The manifest description and main heading are written entirely in Chinese, and the file provides no indication that other languages are supported or that Chinese is required for a region-specific purpose. This creates a natural-language locale constraint without user opt-in, which matches the policy-violation category.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 84% confidence
- Finding
Line L151 states '避免拼音', which is a natural-language constraint on language usage in identifiers. The file does not present this as an optional convention or provide user choice or a documented compliance reason, so it fits the locale/language policy concern.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 93% confidence
- Finding
This code file contains user-facing natural language in Chinese, including the module description and usage notes, which effectively imposes a language/locale on users. The policy allows locale constraints only when they are optional or clearly justified, and neither is present here.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 91% confidence
- Finding
The script prints status, success, and error messages in Chinese, which can force a specific language experience on users. There is no option to switch languages and no justification that this tool is region-specific.
- Content