T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Installation of a Privileged Third-Party Plugin
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent GitLab workflow helper, but it needs review because it combines GitLab write authority, local repository shell commands, and an unpinned third-party plugin.
Install only if you are comfortable granting the MorphixAI integration access to your GitLab account and allowing the agent to run local git commands for selected repositories. Use least-privilege GitLab permissions, prefer a pinned or reviewed plugin version if available, and require explicit approval before actions that approve, merge, retry pipelines, or change MR and issue state.
SKILL.md:17Unpinned Installation of a Privileged Third-Party Plugin
The manifest description and main heading/body are written as mandatory Chinese-facing instructions, with no indication that another language can be used or that the user may choose a locale. This can violate a language/locale policy when a skill effectively constrains interaction language without explicit opt-in or justification.
The skill expands from GitLab API usage into local shell execution and filesystem discovery (nodes.run, find, cd, git fetch, git diff), which materially broadens its authority from remote project operations to local host access. In an adversarial or multi-repo environment, this can expose local repository contents, metadata, branch names, or developer credentials/config context, and it bypasses the stated safety boundary of accessing GitLab only through the MorphixAI proxy.
Lines L223-L234 present manual status verification as mandatory before merging, while L244 states the merge action already performs the check and does not require a manual pre-check. These instructions actively contradict each other and could mislead an agent about the intended safe merge procedure.