T09 · Insecure Skill Coding Practices
- Location
scripts/kimi_runner.py:24- Finding
Command Injection Through Unescaped Task and Working-Directory Inputs
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears purpose-built for running Kimi CLI on coding tasks, but it needs review because it can generate unsafe shell commands and asks for broad local execution authority.
Install only in a controlled environment, prefer a pinned and reviewed Kimi CLI version inside a virtualenv, run it in a dedicated project directory, do not pass untrusted task text or paths through the bundled runner, and verify any background Kimi session is killed after use.
scripts/kimi_runner.py:24Command Injection Through Unescaped Task and Working-Directory Inputs
SKILL.md:217Unpinned Third-Party CLI Installation
The skill explicitly instructs the agent to create/modify files and invoke shell-based tooling, but it does not include a clear safety notice about possible effects on the local filesystem, existing project contents, or installed environment. In practice, this can cause unintended overwrites, dependency changes, or execution in the wrong directory, especially because the skill is designed for autonomous multi-step coding tasks.
The skill documents background interactive sessions and process control, including submit/write/kill operations, but does not prominently warn that these subprocesses may continue running, consume resources, or keep modifying state unless actively monitored and terminated. That creates operational risk: orphaned sessions, unintended long-running tasks, and harder-to-notice ongoing filesystem or environment changes.
No suspicious patterns detected.