T08 · Insecure Dependencies
- Location
SKILL.md:32- Finding
Unpinned Global Installation of a Third-Party Executable Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 32
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code:
bash npm install -g settlemesh@latestTechnical Analysis
The setup instructions install the SettleMesh CLI globally from npm using the mutable
latestdistribution tag. This does not establish a reproducible, reviewed dependency version. Consequently, the code executed during installation and subsequent CLI use may differ from the version that was assessed when the skill was published.An npm package can execute code through installation lifecycle scripts and through its installed command-line entry point. Because the package is installed globally, malicious code would run with the privileges of the user performing the installation and could affect files or commands outside the project directory. The skill subsequently provides the CLI with access to the
SETTLE_API_KEYenvironment variable and an authenticated cached session, increasing the sensitivity of the execution context.The audit found no evidence that the current SettleMesh package is malicious. The issue is the unsafe dependency acquisition practice and the resulting supply-chain exposure.
Attack Path
- An attacker compromises the npm package publisher account, package distribution process, or another component of the dependency supply chain.
- The attacker publishes a malicious release under the
latesttag. - A user follows the documented setup command.
- npm retrieves the attacker-controlled release and installs it globally.
- Malicious lifecycle code may execute during installation, or malicious code may execute when a later
settlemeshcommand is invoked. - The payload runs with the installing user's privileges and may attempt to access the authenticated session,
SETTLE_API_KEY, user files, or other resources available to that account.
Impact Assessment
Succe ...[truncated 651 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version, for example:bash npm install -g settlemesh@1.2.3 - Establish a controlled update process that reviews and tests each new version before changing the documented pin.
- Publish and verify package provenance, integrity metadata, and the identity of the official npm publisher.
- Prefer a project-local installation with a lockfile over a global installation where operationally feasible.
- If the package does not require npm lifecycle scripts, consider installation with
--ignore-scriptsafter confirming that doing so preserves required functionality:bash npm install -g --ignore-scripts settlemesh@1.2.3 - Advise users not to perform the installation as
rootor throughsudo, and run the CLI under a least-privileged account. - Limit the scope and spending authority of API credentials, rotate credentials if compromise is suspected, and protect cached authentication data with restrictive filesystem permissions.
- Replace
