T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Third-Party Installer and Skill Source
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:16
Vulnerability Type: Supply-chain risk from unpinned third-party dependencies
Risk Level: Mediumbash npx skills add nexscope-ai/eCommerce-Skills --skill product-differentiation-tiktok -gTechnical Analysis
The documented installation command invokes the
skillsnpm package throughnpxwithout specifying an exact reviewed version. It also installs skill content fromnexscope-ai/eCommerce-Skillswithout pinning the source to an immutable commit or otherwise documenting integrity verification.Consequently, the code retrieved and used by this command can change after this skill has been reviewed. This creates a supply-chain trust gap: compromise of the npm package, its publishing account, the external repository, or its maintainers could cause users to retrieve and run content different from the audited version. The global installation option (
-g) can increase the affected scope within the invoking user's environment.The audited
scripts/analyzer.pyitself does not retrieve remote payloads or execute subprocesses. The issue is specifically the unsafe installation instruction, not embedded malicious behavior in the analyzer.Attack Path
- An attacker compromises the npm package, its publisher account, the referenced repository, or another relevant upstream distribution channel.
- The attacker publishes or substitutes a malicious release or modifies the repository content.
- A user follows
SKILL.md:16and runs the unpinnednpxcommand. npxresolves the package available at execution time rather than a previously reviewed exact version.- The installation process retrieves the mutable external skill source and installs it globally.
- Malicious upstream installation logic or skill content executes with the privileges of the invoking user or is made available for later invocation.
Impact Assessment
Successful exploitation could permit arbitrary code exec ...[truncated 536 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm installer package to an exact, reviewed version rather than relying on implicit latest-version resolution:
bash npx skills@<reviewed-exact-version> ... - Pin the external skill source to a verified immutable commit or release identifier supported by the installer.
- Publish and verify cryptographic integrity information for downloaded artifacts, such as SHA-256 hashes or signed release attestations.
- Avoid global installation unless it is operationally necessary. Prefer an isolated, least-privileged environment or project-local installation.
- Document the expected package version, repository commit, artifact hash, and verification procedure.
- Re-audit dependency updates before changing any pinned version or source commit.
- Use trusted registries and repository protections such as multi-factor authentication, protected releases, signed commits or tags, and restricted publishing permissions.
- Pin the npm installer package to an exact, reviewed version rather than relying on implicit latest-version resolution:
