T08 · Insecure Dependencies
- Location
SKILL.md:94- Finding
Unpinned Global Installation of a Third-Party CLI
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 94
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: MediumVulnerable Code Snippet:
markdown To enable Ritual Cloud: `npm install -g @ritualai/cli` → `ritual init` → `ritual status`.Technical Analysis
The optional upgrade instructions direct users to install
@ritualai/cliglobally without specifying a reviewed version or verifying package integrity. Consequently, npm resolves the package version associated with the mutable default distribution tag at installation time rather than a version examined during this audit.An npm installation may execute package lifecycle scripts. The global installation option also modifies the user's environment outside the project directory. If the package, one of its transitive dependencies, or its package-registry distribution channel were compromised, installation could execute attacker-controlled code with the permissions of the invoking user.
The subsequent
ritual initcommand may initialize an external service integration in the current workspace. The audited instructions do not explain its network activity or identify what workspace information it may process. No evidence establishes that the named package is currently malicious; this finding concerns the unsafe, unpinned installation pattern and its supply-chain exposure.Attack Path
- An attacker compromises the package, a transitive dependency, a maintainer account, or the relevant registry distribution tag.
- A user follows the documented
npm install -g @ritualai/cliinstruction. - npm resolves and downloads the compromised release because no audited version or integrity value is specified.
- Malicious package code can run during installation through lifecycle scripts or when the installed CLI is invoked.
- The user runs
ritual initandritual status, potentially giving the compromised CLI acce ...[truncated 986 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed release, for example
@ritualai/cli@<audited-version>, rather than relying on a mutable distribution tag. - Record and verify the expected package integrity digest and provenance before installation.
- Prefer a project-local, lockfile-controlled dependency over a global installation so the resolved dependency graph is reproducible and changes remain scoped to the project.
- Where compatible with the package, disable npm lifecycle scripts during installation and explicitly run only the required reviewed entry point.
- Document the CLI's expected network connections, authentication behavior, files accessed or created, and data transmitted by
ritual initandritual status. - Advise users not to run the installation or initialization commands with administrator privileges.
- Re-audit the pinned package and its transitive dependencies before recommending it as part of the skill workflow.
- Pin the CLI to a specifically reviewed release, for example
