T08 · Insecure Dependencies
- Location
SKILL.md:28- Finding
Unpinned Global Installation of an External npm Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 28-31
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: HighVulnerable Code Snippet
markdown ## Setup (once) 1. `npm install -g settlemesh@latest` 2. `settlemesh login` (a human approves once in the browser). 3. Have `claude-code` or `codex` installed **and logged in** on this machine.Technical Analysis
The setup instructions install
settlemesh@latestglobally without an exact version, integrity hash, lockfile, or locally reviewable implementation. The effective code can therefore change after this Skill has been reviewed. Global npm installation may also execute package lifecycle scripts with the privileges of the user performing the installation.The project contains only
SKILL.md, so the external CLI's authentication, credential handling, sandbox enforcement, authorization, network communication, and billing behavior cannot be independently verified from the audited artifact.This is an insecure supply-chain practice rather than proof that the current SettleMesh package is malicious. Nevertheless, it creates a direct execution path from a mutable third-party package registry to the user's machine.
Attack Path
- An attacker compromises the npm publisher account, package distribution infrastructure, or a future release of the dependency.
- The compromised package is published under the
latesttag. - A user follows the Skill's setup instructions and runs
npm install -g settlemesh@latest. - npm downloads the attacker-controlled release and may execute its lifecycle scripts.
- The installed CLI subsequently executes with the user's permissions and can access data and resources available to that user.
Impact Assessment
Successful exploitation could permit arbitrary command execution under the installing user's account. Depending on that account's permissions and environmen ...[truncated 324 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an exact, reviewed version rather than using
@latest. - Publish and verify the expected package integrity hash.
- Use a project-local installation with a committed lockfile instead of a global installation.
- Disable npm lifecycle scripts during installation where operationally possible, then explicitly run only reviewed setup steps.
- Document the authoritative package publisher, registry, expected signatures, and release verification procedure.
- Include or link to auditable source corresponding exactly to the pinned release.
- Run the CLI in a dedicated, minimally privileged account or isolated environment without access to unrelated host credentials.
- Require a security review before upgrading the pinned dependency.
- Pin the dependency to an exact, reviewed version rather than using
