T08 · Insecure Dependencies
- Location
SKILL.md:39- Finding
Unpinned Third-Party CLI Installation and Automatic Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent RunComfy video-extension helper, with disclosed CLI, network, and token use, but users should be cautious about the unpinned npm install path.
Before installing, verify the @runcomfy/cli package source and consider pinning a reviewed version instead of running unversioned npm or npx commands. Use a token with only the access you need, avoid placing secrets in prompts or logs, and only extend video URLs you intentionally provide.
SKILL.md:39Unpinned Third-Party CLI Installation and Automatic Execution
The manifest lists several specific trigger phrases, but then broadens activation to "any explicit ask to take an existing video and add more frames after it." That catch-all condition is ambiguous and lacks clear boundaries or exclusion examples, which could cause the skill to match a wide range of ordinary requests about editing or lengthening video.
The skill recommends executing npx -y @runcomfy/cli without pinning a specific version, which allows whatever the latest published package is at execution time to run on the user's system. If the package is compromised upstream, typosquatted, or a malicious version is published, the agent/operator could execute attacker-controlled code during setup.
In the security section, the skill still endorses npx -y @runcomfy/cli as a safe install path without version pinning. Even though the surrounding guidance is security-conscious, invoking an unpinned remote package still creates a supply-chain execution risk because the fetched code can change over time.