T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unpinned Globally Installed Executable Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 18
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: MediumVulnerable Code
yaml - npm install -g clawdcursorTechnical Analysis
The installation instruction retrieves the latest available version of the
clawdcursornpm package and installs its executable globally. It does not specify a version or integrity hash. The project contains onlySKILL.md; it provides no package lockfile, vendored implementation, or source code with which to verify the installed executable's behavior.This creates a time-of-review/time-of-installation supply-chain risk. The package installed by a user may differ from the version described and audited in the Skill documentation. A compromised maintainer account, npm package, or later malicious release could therefore introduce arbitrary code without requiring any change to this repository.
Although the metadata identifies Skill version
0.7.5, the installation command does not constrain npm to the corresponding package version. The documentation subsequently directs users to grant desktop-control consent and run the installed executable, increasing the security significance of the unpinned dependency.Attack Path
- An attacker compromises the npm package, its maintainer account, or a future release process.
- The attacker publishes a malicious version under the existing
clawdcursorpackage name. - A user follows the documented
npm install -g clawdcursorinstruction. - npm resolves and globally installs the attacker-controlled current release.
- The user runs
clawdcursor consent --acceptand startsclawdcursor serve,clawdcursor mcp, orclawdcursor start. - The malicious executable runs with the user's privileges and can misuse the desktop-automation access granted to it.
Impact Assessment
Successful exploitation could provide arbitrary code execution ...[truncated 641 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin the dependency to the reviewed release, such as:
bash npm install -g clawdcursor@0.7.5 -
Publish and verify a cryptographic integrity hash or signed release artifact before installation.
-
Include auditable source code, a package manifest, and a lockfile in the reviewed project so the executable dependency graph can be assessed.
-
Prefer a project-local installation over a global installation where practical, and invoke the pinned binary from that isolated environment.
-
Use npm provenance, package signatures, and a trusted registry policy to reduce maintainer-account and registry compromise risks.
-
Require explicit review of requested desktop-control permissions rather than encouraging automatic consent.
-
Ensure the documented Skill version and installed package version are kept synchronized through automated release checks.
-
