T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Unpinned Third-Party Package Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 24
Vulnerability Type: Unpinned npm dependency executed throughnpx
Risk Level: MediumVulnerable Code
text openclaw mcp add sentvia --command npx --arg -y --arg sentvia-mcpTechnical Analysis
The setup instruction configures an MCP server by downloading and executing the
sentvia-mcpnpm package without specifying a version or verifying its integrity. The-yoption also suppresses the normal installation confirmation.Because the package source is not included in the audited project and no version or integrity hash is specified, the code executed by this command can change after the skill has been reviewed. This creates a supply-chain trust boundary around the npm registry, the package publisher account, and the package's transitive dependencies.
This is an insecure dependency configuration rather than evidence that the current
sentvia-mcppackage is malicious.Attack Path
- An attacker compromises the npm publisher account, package, registry delivery path, or a relevant dependency.
- The attacker publishes a malicious release under the existing
sentvia-mcppackage name. - An operator follows the documented setup command.
npx -yretrieves the package selected by npm's unpinned version resolution and executes it without an interactive confirmation.- The executed package runs with the privileges and environment of the agent process.
- Because the instructions require placing
SENTVIA_API_KEYin the MCP server environment, malicious package code could read and exfiltrate that credential. - The attacker could then use the exposed credential to perform email operations allowed by the associated SentVia account.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user running OpenClaw or
npx. The accessible scope may include:- The
SENTVIA_API_KEYsupplied to the MCP server. - SentVia ...[truncated 383 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
sentvia-mcpto a reviewed, immutable version rather than relying on npm's default version resolution. - Maintain a lockfile and verify the package and transitive-dependency integrity hashes.
- Document the official npm package URL, expected publisher identity, and approved version.
- Remove
-ywhere practical so package installation is not silently approved. - Install dependencies during a controlled deployment phase rather than dynamically at skill invocation time.
- Review new package versions before updating the approved pin.
- Run the MCP server in a sandbox or dedicated low-privilege account with restricted filesystem and network access.
- Expose only
SENTVIA_API_KEYto the MCP process and avoid inheriting unrelated credentials or sensitive environment variables. - Restrict the SentVia credential to the minimum permissions required and rotate it if package compromise is suspected.
- Pin
