T08 · Insecure Dependencies
- Location
SKILL.md:26- Finding
Unpinned Remote Repository and Unaudited npm Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 26–27
Vulnerability Type: Unpinned remote source and unsafe dependency installation
Risk Level: Mediumbash git clone https://github.com/Tryboy869/context-manager-agentic cd context-manager-agentic && npm installTechnical Analysis
The skill delegates its functionality to a mutable external GitHub repository and does not pin the cloned content to a reviewed commit SHA or signed release. Consequently, the code retrieved by users can differ from the code that existed when the skill documentation was reviewed.
The subsequent
npm installcommand resolves packages using manifests supplied by that remote repository. It may also execute npm lifecycle scripts, such aspreinstall,install, andpostinstall, with the permissions of the installing user. The local skill package does not contain the referenced implementation, dependency manifest, or lockfile, so the dependency graph, lifecycle scripts, and effective executable behavior cannot be audited from this artifact.This creates a supply-chain trust gap: compromise of the GitHub account, repository, release process, npm dependencies, or transitive dependencies could introduce executable code without any modification to the reviewed
SKILL.mdfile.Attack Path
- An attacker compromises the referenced GitHub repository, its owner account, or one of its npm dependencies.
- The attacker adds a malicious dependency, lifecycle script, or modification to
cli.js. - A user follows the documented instructions and clones the repository's current mutable state.
- The user runs
npm install, causing attacker-controlled package code or lifecycle scripts to execute, or later invokes the modifiedcli.js. - The malicious code runs with the user's privileges and can access resources available to that process.
Impact Assessment
Successful exploitation could permit arbitrary cod ...[truncated 715 chars]
- Remediation
View remediation
Remediation Suggestions
- Include the complete implementation and dependency metadata in the skill package so that the effective behavior can be reviewed together with
SKILL.md. - Pin the external repository to a specific, reviewed commit SHA rather than cloning the default branch.
- Prefer a signed release artifact and verify its cryptographic signature or published checksum before use.
- Commit a reviewed
package-lock.jsonand replacenpm installwithnpm cito enforce the locked dependency graph. - Audit all direct and transitive dependencies for known vulnerabilities, suspicious maintainers, dependency confusion, and typosquatting.
- Review all npm lifecycle scripts and use
npm ci --ignore-scriptswhere installation scripts are unnecessary. - Run installation and execution in a sandbox or container with minimal filesystem access, no unnecessary credentials, restricted network access, and a non-privileged user.
- Establish a controlled update process in which new repository commits and dependency-lock changes are reviewed before the pinned version is advanced.
- Include the complete implementation and dependency metadata in the skill package so that the effective behavior can be reviewed together with
