T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned Third-Party Dependencies Installed with Global Scope
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:19-22, with additional occurrences atSKILL.md:353-362
Vulnerability Type: Unpinned third-party dependency and mutable skill source
Risk Level: MediumVulnerable Code
Primary installation command:
bash npx skills add nexscope-ai/eCommerce-Skills --skill ecommerce-advertising -gAdditional recommended installation commands:
bash npx skills add nexscope-ai/eCommerce-Skills --skill ecommerce-ppc-strategy-planner -gbash npx skills add nexscope-ai/Amazon-Skills --skill amazon-ppc-campaign -gTechnical Analysis
The documented commands invoke the
skillspackage throughnpxwithout pinning the package to a verified version. They also identify third-party skill repositories by mutable repository names rather than immutable commit hashes or signed releases.Consequently, the components retrieved when a user runs these commands can differ from the components reviewed during this audit. The
-goption gives the installation global scope within the applicable skill environment, increasing the reach and lifetime of any compromised content.This is a supply-chain trust issue. An npm package compromise, repository account takeover, malicious upstream release, or unauthorized modification of the referenced skill could introduce behavior not present in the audited project. The current artifact does not itself contain a malicious payload, and exploitation therefore depends on a future or existing compromise of an external distribution source.
Attack Path
- An attacker compromises the npm package resolved by
npx, an associated publishing account, or one of the referenced third-party repositories. - The attacker publishes a modified package or skill containing malicious installation logic or hostile skill instructions.
- A user follows one of the documented commands.
npxresolves and runs the unpinned package, w ...[truncated 966 chars]
- An attacker compromises the npm package resolved by
- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsCLI to an explicitly reviewed version, for example by using a version-qualified package reference rather than an unversionednpx skillsinvocation. - Pin each referenced skill repository to an immutable commit hash or cryptographically signed release tag.
- Publish and verify checksums or signatures for downloaded skill artifacts before installation.
- Replace global installation with a project-local or isolated installation unless global availability is strictly required.
- Run installation with a non-privileged account and restrict filesystem, network, and credential access through sandboxing.
- Configure package-manager lockfiles and approved registries where supported.
- Audit installation scripts and retrieved skill contents before activation.
- Document the expected package publisher, repository owner, version, commit, and integrity hash so users can detect unexpected source changes.
- Apply the same controls to the related-skill commands at
SKILL.md:353-362.
- Pin the
