T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned Global Installation of a Third-Party CLI Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 25-26
Vulnerability Type: Supply-chain exposure through an unpinned global dependency
Risk Level: MediumVulnerable Code
markdown **If not installed, run the folling:** `npm install -g @privacy-com/privacy-cli`Technical Analysis
The Skill instructs the agent to install the latest available version of
@privacy-com/privacy-cliglobally. It does not pin an audited version, verify package integrity, use a lockfile, or require approval immediately before installation.A global npm installation can run package lifecycle scripts under the privileges of the user running the agent. Although the package name is consistent with the declared Privacy.com integration, its effective contents may change after the Skill has been reviewed. Compromise of the package, publisher account, or registry delivery path could therefore introduce arbitrary executable code.
This is especially sensitive because the installed CLI is expected to access
PRIVACY_API_KEY, Privacy.com card records, transaction information, and potentially complete payment-card credentials.Attack Path
- An attacker compromises the package, its publisher account, or its dependency chain.
- A user invokes the Skill on a system where the
privacycommand is absent. - The agent follows the installation instruction and retrieves the current package release with
npm install -g. - Malicious package code or an npm lifecycle script executes under the user's account.
- The code reads accessible credentials or data, including
PRIVACY_API_KEYor~/.privacy/config. - The compromised CLI may subsequently intercept card-management commands, transaction results, or PAN output.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the permissions of the user running npm. The attacker could access files and environment variables available to ...[truncated 412 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specific version that has been reviewed, for example
@privacy-com/privacy-cli@<approved-version>. - Verify the package against an expected registry, publisher identity, and integrity hash.
- Prefer a project-local installation governed by a lockfile instead of a global installation.
- Disable lifecycle scripts during installation when compatible with the package.
- Require explicit user approval before installing or upgrading executable dependencies.
- Execute the CLI in a restricted environment with access only to the required credential and resources.
- Establish a controlled update process that reviews new package versions before changing the pin.
- Pin the CLI to a specific version that has been reviewed, for example
