T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:892
- Finding
- Unpinned Third-Party Installation Through npx## Vulnerability Details **File Location**: `SKILL.md`, line 892 **Vulnerability Type**: Unpinned and unaudited third-party dependency execution **Risk Level**: Medium ### Vulnerable Code Snippet ```text Fix: `npx skills add ofoxai/skills` (the whole repo). ``` ### Technical Analysis The recovery instructions recommend invoking `npx` to install an entire external repository. The command does not pin an immutable package version or source commit and does not require checksum or signature verification. Because the external package and the referenced image and video core scripts are absent from this artifact, their lifecycle behavior, network destinations, credential handling, filesystem operations, and transitive dependencies cannot be audited here. The instruction also installs the whole repository rather than only the two core components required by this Skill, unnecessarily increasing the supply-chain attack surface. This is an insecure dependency pattern rather than evidence that the current upstream is malicious. Exploitation would require the package, its distribution channel, or one of its dependencies to become compromised or resolve to attacker-controlled content. ### Attack Path 1. The expected sibling core scripts are missing. 2. An Agent follows the documented recovery instruction. 3. `npx` resolves mutable external package content without an immutable version or integrity constraint. 4. A compromised package, registry account, distribution channel, or transitive dependency supplies malicious code. 5. The retrieved code executes during installation or subsequent Skill use with the Agent process's privileges. 6. That code may access data available to the process, including `OFOX_API_KEY`, user-provided media, generated artifacts, and writable project files. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the privileges of the user running the Agent. The resulting scope may include: - Reading and exfi ...[truncated 419 chars]
- Remediation
- ## Remediation Suggestions 1. Pin the dependency to an audited, immutable package version and source commit rather than resolving the latest mutable content. 2. Publish and verify cryptographic checksums or signatures before installation. 3. Use an explicit trusted registry and disable unexpected lifecycle scripts where supported. 4. Install only the required `ofox-image-core` and `ofox-video-core` components instead of the entire repository. 5. Commit a lockfile covering direct and transitive dependencies. 6. Vendor the required audited scripts into the distributed package when licensing and maintenance constraints permit. 7. Document the expected installed files and verify their hashes before execution. 8. Run installation and generation components with least privilege and a restricted environment that exposes only `OFOX_API_KEY` and the files necessary for the current task.