T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Global npm Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 5
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: MediumVulnerable Code Snippet:
yaml compatibility: "Requires the settlemesh CLI (npm i -g settlemesh) and a SETTLE_API_KEY; makes authenticated, metered calls to the SettleMesh platform over the network."Technical Analysis
The skill directs users to install the
settlemeshnpm package globally without specifying an exact version, lockfile, integrity hash, or other provenance verification. Consequently, the code installed and executed may differ from the version assessed during this audit.npm packages can execute lifecycle scripts during installation. If the package, its publisher account, registry entry, or a transitive dependency is compromised, a later installation could execute attacker-controlled code with the privileges of the user running npm. Global installation also places the executable in a shared command path, increasing its reach beyond this individual skill invocation.
Attack Path
- An attacker compromises the
settlemeshnpm package, its publisher account, or a dependency included in a later release. - The attacker publishes a malicious package version or introduces a malicious installation lifecycle script.
- A user or agent follows the documented command:
bash npm i -g settlemesh - npm retrieves the current unpinned release and executes its installation behavior.
- Attacker-controlled code runs with the installing user's privileges.
- The malicious code may inspect accessible files, npm configuration, cached SettleMesh sessions, or environment variables such as
SETTLE_API_KEY, and may replace the globally availablesettlemeshexecutable.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's account. The affected scope may include readab ...[truncated 469 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to an exact reviewed version, for example:
bash npm install --global settlemesh@X.Y.Z - Document the expected package integrity hash and verify package provenance before installation.
- Prefer a project-local, lockfile-controlled dependency over global installation where operationally possible.
- Install and execute the CLI in a restricted environment with only the minimum filesystem, network, and credential access required.
- Review the package's lifecycle scripts and transitive dependency tree before approving version upgrades.
- Avoid exposing
SETTLE_API_KEYduring installation; provide it only to the reviewed executable at runtime. - Establish an explicit upgrade process so newly published versions are reviewed before the pinned version is changed.
- Pin the CLI to an exact reviewed version, for example:
