T03 · Remote Payload Retrieval and Execution
- Location
references/setup.md:63- Finding
Unpinned Remote Runtime Retrieval and Execution
- Content
View full analysis
Vulnerability Details
File Location:
references/setup.md:63-69andreferences/setup.md:81-85
Vulnerability Type: Remote payload retrieval and supply-chain exposure
Risk Level: HighVulnerable Code
bash git clone https://github.com/abu-ShotAI/ai-video-remix.git cd ai-video-editor npm install cp .env.example .envThe subsequently retrieved runtime is executed as follows:
bash # Test skill (heuristic mode, no LLM needed) AGENT_PROVIDER=none npx tsx src/skill/cli.ts "test run" --composition TravelVlogEquivalent cloning, dependency installation, and runtime execution instructions also appear in
SKILL.md:46-52.Technical Analysis
The audited package is instruction-only and does not contain the runtime implementation it directs users to execute. Its setup procedure clones the mutable default branch of an external Git repository without pinning a reviewed commit hash or verified release artifact. It then runs
npm installand executes the remotely obtained TypeScript CLI.This creates a time-of-check/time-of-use trust gap: the code executed by a user can differ from the code that existed when this skill was reviewed. A repository compromise, malicious upstream change, or dependency compromise could therefore alter the effective payload after publication of the skill. In addition,
npm installcan execute package lifecycle scripts unless explicitly restricted.Because neither the external runtime source nor its dependency lockfile is included in the audited artifact, the claims concerning localhost-only network binding, credential scoping, filesystem behavior, and external communication cannot be independently verified from this package.
The documented
git clonecommand also names the repositoryai-video-remix, while the next command entersai-video-editor. This inconsistency may encourage users to improvise during installation, although it is primarily a reliability i ...[truncated 1399 chars]- Remediation
View remediation
Remediation Suggestions
- Bundle the reviewed runtime source in the skill package so its behavior can be audited together with the instructions.
- If remote retrieval remains necessary, pin the repository to a specific reviewed commit hash rather than cloning a mutable default branch.
- Publish signed or checksummed release archives and require users to verify their integrity before execution.
- Include a committed dependency lockfile and use
npm cirather thannpm installto obtain deterministic dependency versions. - Review dependency lifecycle scripts and use
npm ci --ignore-scriptswhere installation scripts are not required. - Pin CI and release dependencies, monitor them for known vulnerabilities, and apply automated dependency integrity checks.
- Correct the cloned directory name so the documented setup is deterministic.
- Avoid making definitive security claims about credential handling, network binding, or filesystem access unless the corresponding pinned runtime implementation is included in the audit scope.
- Recommend executing the runtime with least privilege, restricted filesystem access, and only the credentials needed for the current operation.
