T08 · Insecure Dependencies
- Location
SKILL.md:67- Finding
Unpinned npm Package Downloaded and Executed Automatically
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 67–70
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: Mediumbash openclaw mcp set context-mode '{"command":"npx","args":["-y","context-mode"]}' openclaw gateway restartTechnical Analysis
The installation instructions configure OpenClaw to execute
context-modethroughnpxwithout specifying an exact package version. The-yoption suppresses the normal confirmation prompt. No lockfile, package integrity hash, vendored implementation, or other provenance control is present in the audited project.As a result, the package executed by users may differ from the version that existed when this Skill was reviewed. A compromised package release, npm maintainer account, transitive dependency, or package-distribution channel could introduce arbitrary code without requiring changes to
SKILL.md.The advertised MCP server processes shell output, file content, and fetched web material. Although the audited file contains no evidence that it exfiltrates such information, a compromised future package could misuse this access. The risk arises from unsafe dependency retrieval rather than confirmed malicious behavior in the reviewed Skill.
Attack Path
- An attacker compromises the
context-modenpm package, a maintainer account, or a dependency included by a future release. - The attacker publishes a malicious version under the same package name.
- A user follows the documented configuration command, which does not constrain package resolution to an audited version.
- When OpenClaw starts the configured MCP server,
npx -y context-moderetrieves and executes the package without an interactive confirmation. - Malicious package code runs with the privileges of the OpenClaw process and may access resources available to that user and process.
Impact Assessment
Successful exploitation could permit arbitrary code ...[truncated 580 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
context-modeto a specific, audited version rather than resolving the latest available release. - Verify package provenance and integrity through trusted registry metadata, cryptographic integrity values, signatures, or an equivalent verification mechanism.
- Maintain lockfile or integrity metadata for the package and its transitive dependencies where the deployment model permits it.
- Review the selected package version and dependency tree before recommending installation.
- Avoid
-ywhere practical so unexpected package acquisition remains visible to the user. - Run the MCP server under a dedicated, least-privileged account or sandbox with narrowly scoped filesystem and network access.
- Restrict access to sensitive repositories, credentials, environment variables, and unrelated user files.
- Document what information is indexed, where the SQLite database is stored, how long indexed data persists, and whether any data leaves the local environment.
- Establish a controlled update process in which new package versions are reviewed and explicitly approved before deployment.
- Pin
