T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:64- Finding
Execution of Unpinned Remote Code Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 64–73
Vulnerability Type: Unpinned retrieval and execution of code from a third-party GitHub repository
Risk Level: HighVulnerable Code
bash openclaw mcp add seevido \ --command npx \ --arg -y \ --arg github:gpt-img-2/seevido-prompt-mcp \ --include 'build_video_prompt,plan_reference_sequence,diagnose_video_prompt,get_seevido_resources'bash npx -y github:gpt-img-2/seevido-prompt-mcpTechnical Analysis
The Skill directs users to retrieve and execute an MCP package directly from
github:gpt-img-2/seevido-prompt-mcp. The repository reference is not pinned to an immutable commit hash or an integrity-verified release artifact. Consequently, the code executed by users can change after the Skill has been reviewed.The
npx -yoption suppresses the normal installation confirmation, reducing the opportunity for users to inspect the package source or notice an unexpected dependency change. Depending on the package configuration, executable code may run through package lifecycle scripts or when the MCP server starts.This is best classified as remote payload retrieval and execution because the effective executable payload resides outside the audited project and remains mutable.
Attack Path
- An attacker compromises the referenced GitHub repository, its maintainer account, or another mechanism controlling its default branch.
- The attacker modifies the MCP package or one of its dependencies to include malicious lifecycle or runtime code.
- A user follows the installation instructions in
SKILL.md. npx -ydownloads the repository's current, potentially modified contents without an interactive confirmation.- The malicious code executes under the account and environment used to launch OpenClaw or
npx. - The code can access resources available to that process, subject to operating-system permissions and any applicable sandboxing.
Impact Assessme
...[truncated 592 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the GitHub dependency to a reviewed, immutable full commit hash rather than the repository's mutable default branch.
- Prefer a signed and versioned release artifact with a published cryptographic checksum or package-manager integrity metadata.
- Remove
-yso users must explicitly approve installation after reviewing the resolved source and version. - Audit the package's source, transitive dependencies, lifecycle scripts, and MCP startup behavior before recommending execution.
- Document the expected commit hash and provide checksum or signature verification steps.
- Run the MCP server with least privilege in an isolated environment that has restricted filesystem, credential, and network access.
- Establish a controlled update process in which new commits or releases are reviewed before the pinned reference is changed.
