T08 · Insecure Dependencies
- Location
- SKILL.md:565
- Finding
- Unpinned and Overbroad Global Dependency Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 565–568 **Vulnerability Type**: Unsafe third-party dependency installation **Risk Level**: Medium ### Vulnerable Code ```text - **The probe printed nothing** — `ofox-video-core` really is absent, and the fix belongs to whichever installer the user already has: `npx ofox-skills` (this repo's own) or the underlying `npx skills add ofoxai/skills --skill '*' --agent '*' --global --yes` for skills.sh; on LobeHub or ClawHub, install `ofox-video-core` from the same publisher. ``` ### Technical Analysis The documented recovery procedure invokes npm-delivered command-line packages through `npx` without pinning an audited package version or verifying package integrity. An unpinned `npx` invocation can retrieve and execute a newer package release whose contents differ from those reviewed. The second command further uses `--skill '*'`, `--agent '*'`, `--global`, and `--yes`. This installs every available skill from the publisher for all supported agents at global scope, suppressing interactive confirmation, even though the documented feature only requires `ofox-video-core`. This violates least-dependency principles and unnecessarily expands the trusted supply chain and installed capability set. The commands are presented as manual recovery instructions rather than silently executed code. Exploitation therefore depends on an Agent or user following the instructions when the core dependency is absent. ### Attack Path 1. The required `ofox-video-core` dependency is missing. 2. An Agent or user follows the documented fallback installation procedure. 3. `npx` resolves and downloads the current, unpinned installer package. 4. npm package lifecycle or installer code executes with the invoking user's privileges. 5. If the fetched package or publisher distribution has been compromised, attacker-controlled code executes locally. 6. The wildcard global command additionally installs all publisher-provided ...[truncated 1010 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the installer to a reviewed version rather than resolving the latest release implicitly, for example by using an exact package version. 2. Verify the downloaded package using a trusted lockfile, registry integrity metadata, signature, or published checksum before execution. 3. Install only the required `ofox-video-core` skill instead of using `--skill '*'`. 4. Limit installation to the specific Agent that needs the dependency instead of using `--agent '*'`. 5. Prefer a project-local or user-scoped installation over `--global`. 6. Remove `--yes` so users can review the package source, version, scope, and requested changes before installation. 7. Require explicit user approval before initiating any package installation. 8. Prefer a verified local package, vendored audited dependency, or signed official release artifact where available. 9. Document the exact trusted publisher identity and minimum compatible version, then fail safely if verification cannot be completed.
