T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Third-Party Installation Chain
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 15
Vulnerability Type: Unpinned executable package and mutable remote repository installation
Risk Level: MediumVulnerable Code
bash npx skills add nexscope-ai/eCommerce-Skills --skill supply-chain-optimization-walmart -gTechnical Analysis
The documented installation command invokes
npxwithout pinning theskillspackage to an audited version. Depending on the local environment and npm behavior,npxmay retrieve and execute the current package release from the configured npm registry.The command also identifies the
nexscope-ai/eCommerce-Skillsrepository without specifying an immutable commit or content digest. Consequently, the code or instructions installed by this command may differ from the content reviewed during this audit. The-goption additionally installs the resulting Skill globally, increasing its availability and exposure beyond a single isolated project.This is a supply-chain trust issue rather than evidence that the currently bundled calculator is malicious. No malicious behavior was identified in
scripts/calculator.py.Attack Path
- An attacker compromises the publisher account, package, registry delivery path, or referenced repository.
- The attacker publishes a malicious
skillspackage release or modifies the repository content referenced by the mutable repository name. - A user follows the installation command from
SKILL.md. npxretrieves and executes the unpinned CLI package.- The CLI retrieves mutable Skill content and installs it globally.
- Malicious installer logic may execute immediately with the invoking user's privileges, or malicious Skill instructions and scripts may become available during subsequent agent sessions.
Successful exploitation depends on compromise or malicious mutation of an upstream dependency; the reviewed artifact does not itself perform this compromise.
Impact Assessment
A comprom ...[truncated 605 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI package to a reviewed, exact version, for example
npx skills@X.Y.Z, rather than resolving the latest available release. - Pin the Skill repository content to an immutable commit identifier or signed release tag.
- Verify package integrity through lockfiles, registry integrity hashes, provenance attestations, or cryptographic signatures.
- Avoid global installation by default. Prefer a project-local, isolated installation with the minimum required permissions.
- Review the CLI package and resolved Skill content before execution, especially installation hooks and files under
scripts/. - Use a trusted registry and repository source, enable publisher multi-factor authentication, and monitor upstream releases for unauthorized changes.
- Document the exact expected package version, repository revision, and integrity value so users can reproduce the audited installation.
- Pin the CLI package to a reviewed, exact version, for example
