T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:26- Finding
Execution of a Mutable Remote npm Package Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 26–27
Vulnerability Type: Remote payload retrieval and execution through an unpinned dependency
Risk Level: Mediumjson "command": "npx", "args": ["-y", "mcp-remote@latest", "https://gateway.pipeworx.io/onthisday/mcp"]Technical Analysis
The documented configuration invokes
npxwith the-yoption, which suppresses interactive confirmation and permits npm to retrieve and execute the specified package automatically. The package is referenced using the mutable@latesttag rather than an audited, exact version.Consequently, the code executed by users can change after this skill has been reviewed. The project does not provide a lockfile, package-integrity hash, vendored implementation, or other mechanism to ensure that the downloaded package is identical to a previously audited release.
The process also connects to the external endpoint
https://gateway.pipeworx.io/onthisday/mcp. This is consistent with the documented integration, but the locally executedmcp-remotepackage remains part of the trusted execution path.Attack Path
- An attacker compromises the
mcp-remotenpm package, its maintainer account, its publishing credentials, or a future release distributed under thelatesttag. - A user installs or starts the skill using the documented MCP configuration.
npx -yretrieves the version currently referenced bymcp-remote@latestwithout requesting confirmation.- npm package installation hooks or runtime code execute under the local user's account.
- Malicious package code accesses resources available to that account or communicates with attacker-controlled infrastructure.
Impact Assessment
Successful exploitation could allow arbitrary code execution with the privileges of the user running the MCP client. Depending on that user's environment, the accessible scope could include local files, environment variables, application credentials, API t ...[truncated 331 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
mcp-remote@latestwith an exact, reviewed version such asmcp-remote@X.Y.Z. - Install the dependency through a committed lockfile and require integrity verification during installation.
- Avoid
npx -yfor security-sensitive integrations. Prefer a locally installed and reviewed executable whose version is controlled by the project. - Review the selected package version, including installation scripts, transitive dependencies, and network behavior, before deployment.
- Run the MCP process in a restricted environment with minimal filesystem permissions, a sanitized environment, limited credentials, and network access restricted to required destinations.
- Establish a controlled update process in which new package versions are reviewed and tested before the pinned version is changed.
- Replace
