T08 · Insecure Dependencies
- Location
README.md:24- Finding
Unpinned Third-Party Installer and Mutable Remote Skill Source
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 24
Vulnerability Type: Unpinned third-party dependency and mutable remote source
Risk Level: Mediumbash npx skills add aituberapp/ai-video-skillTechnical Analysis
The documented installation command invokes
npxwithout pinning theskillspackage to a reviewed version. Depending on the local environment and npm cache state,npxmay retrieve and execute the latest available package release. The repository shorthandaituberapp/ai-video-skillalso identifies mutable remote content rather than a specific reviewed commit.Consequently, the code executed by the installer and the Skill content ultimately installed can change after this repository has been audited. Neither the installer implementation nor its dependency tree is included in the audited project, so their security cannot be established from the available files. This creates a supply-chain trust boundary in which a compromised npm release, transitive dependency, package ownership change, or remote repository revision could introduce attacker-controlled behavior.
The audit did not establish that the current package or repository is malicious. The vulnerability is the unsafe reliance on unpinned, remotely mutable components during installation.
Attack Path
- An attacker compromises the
skillsnpm package, one of its dependencies, its publishing credentials, or the referenced remote repository. - The attacker publishes a malicious package version or modifies the repository content resolved by
aituberapp/ai-video-skill. - A user follows the README and runs
npx skills add aituberapp/ai-video-skill. npxretrieves the unpinned installer package, or uses an unreviewed version not covered by this audit.- The installer runs with the invoking user's privileges and retrieves mutable Skill content.
- Malicious installer code could execute immediately, or altered Skill in ...[truncated 914 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Pin the npm installer to an exact, reviewed version, for example:
bash npx --yes skills@<reviewed-exact-version> add ...Do not use version ranges or tags such as
latest. -
Pin the Skill source to a specific reviewed commit rather than a branch or repository shorthand. Document the expected commit identifier.
-
Publish and verify cryptographic integrity information for the installer and downloaded Skill content. Where supported, use npm provenance, signed releases, checksums, or Sigstore-based verification.
-
Review and lock the installer's complete dependency tree. Use a lockfile and automated dependency monitoring, and prevent unexpected lifecycle scripts where practical.
-
Make the non-executing manual installation method the preferred approach. Instruct users to download a specific release or commit, verify its checksum, inspect
SKILL.md, and then copy it into the appropriate Skill directory. -
Recommend executing installation in a restricted environment without unnecessary credentials or elevated privileges. Users should not run the command as root or with administrator permissions.
-
Update the documentation to explain that
npxexecutes third-party code and that repository branches are mutable, enabling users to make an informed trust decision.
-
