T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:542
- Finding
- Unpinned Third-Party Packages Used for Unattended Global Skill Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 542-545 **Vulnerability Type**: Unpinned and overly broad third-party dependency installation **Risk Level**: Medium ### Vulnerable Code ```text 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 skill directs users or agents to invoke packages through `npx` without pinning an audited version or verifying package integrity. The second command also uses `--skill '*'`, `--agent '*'`, `--global`, and `--yes`, causing every available skill from the publisher to be installed globally and without an interactive confirmation step. Because npm package names and publisher content are mutable, the code executed by these commands may differ from the version reviewed when this skill was published. The installed `ofox-video-core` dependency is especially security-sensitive because the audited documentation delegates API-key handling, image uploads, network requests, polling, and file downloads to that component. Its implementation is not included in this project and therefore could not be verified during this audit. This is a supply-chain weakness rather than evidence that the current publisher or dependency is malicious. Exploitation would require compromise of the relevant package, publisher account, distribution channel, or a future package release. ### Attack Path 1. An attacker compromises the npm package, its publisher account, or another source used to distribute `ofox-video-core` or the associated skill collection. 2. The attacker publishes a malicious version under the expected package or publisher identity. 3. The local core script is unavailable, causing the user or agent to follow the installation recovery instr ...[truncated 1354 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the installer and dependency to explicitly reviewed versions, for example by using an exact package version rather than the mutable latest release. 2. Record and verify npm integrity hashes or signed release artifacts before executing downloaded package code. 3. Install only the required `ofox-video-core` skill instead of using `--skill '*'`. 4. Restrict installation to the specific Agent that needs the dependency instead of using `--agent '*'`. 5. Avoid global installation unless it is operationally necessary; prefer a project-scoped, isolated dependency directory. 6. Remove `--yes` where practical so users can review the package identity, version, requested scope, and installation target. 7. Vendor the reviewed `ofox-video-core` implementation with the skill, or provide a lockfile and reproducible installation procedure. 8. Run installation and video-generation components with least privilege and expose only the specific files and environment variables required for the task. 9. Document the trusted package name, expected publisher identity, minimum secure version, checksum, and verification procedure.