T08 · Insecure Dependencies
- Location
references/cli-common.md:8- Finding
Execution of an Unpinned Third-Party CLI Package
- Content
View full analysis
Vulnerability Details
File Locations:
references/cli-common.md:8-10references/cli-common.md:18references/cli-common.md:37references/api-guide.md:7-8
Vulnerability Type: Unpinned remote npm dependency execution
Risk Level: MediumVulnerable Code
references/cli-common.md:8-10:bash npx @delilegal/deli-cli@latest checkreferences/cli-common.md:18:bash npx @delilegal/deli-cli@latest init --apikey "Your API Key"references/cli-common.md:37:bash npx @delilegal/deli-cli@latest cmds case-retrieval-report@1.0.0references/api-guide.md:7-8:bash npx @delilegal/deli-cli@latest cmds case-retrieval-report@1.0.0 npx @delilegal/deli-cli@latest run_... <command> [options]Technical Analysis
The Skill requires
npxto retrieve and execute@delilegal/deli-cliusing the mutable@latestdistribution tag. The project does not pin an audited package version, provide a lockfile, specify an integrity hash, or include the CLI source for review.Consequently, the code executed during a future Skill invocation may differ from the package version that existed when this audit was performed. A compromised npm publisher account, malicious package update, registry compromise, or upstream dependency compromise could cause arbitrary JavaScript lifecycle or CLI code to execute locally.
The risk is elevated because the CLI is used for authentication and legal case retrieval. It may receive an API key and confidential case facts, while npm package code executes with the permissions of the user running the Agent.
Attack Path
- An attacker compromises the npm publisher account, package distribution process, or an upstream dependency of
@delilegal/deli-cli. - The attacker publishes a malicious release and assigns it to the
latestdistribution tag. - A user invokes the case-retrieval Skill.
- The documented workflow runs
npx @delilegal/deli-cli@latest, causing npm to retrieve and exe ...[truncated 1108 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace
@latestwith an exact, reviewed version, for example:bash npx --yes @delilegal/deli-cli@1.2.3 check -
Record and verify the expected package integrity hash through a lockfile or another trusted integrity-verification mechanism.
-
Prefer a locally installed, locked dependency or a vetted bundled binary rather than downloading executable code during every invocation.
-
Establish a controlled upgrade process in which each new CLI version is reviewed and tested before the pinned version is changed.
-
Verify and document the expected npm publisher, registry, package provenance, and backend endpoints.
-
Run the CLI in a restricted environment with only the filesystem and network permissions required for case retrieval.
-
Avoid placing API keys directly in command-line arguments, where they may be exposed through shell history or process listings. Use protected standard input, an environment-specific secret provider, or a permission-restricted credential store supported by the CLI.
-
Warn users before confidential legal materials are transmitted to an external service, and minimize submitted case data to what is necessary for retrieval.
-
