T08 · Insecure Dependencies
- Location
SKILL.md:35- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:35
Vulnerability Type: Supply-chain exposure through an unpinned third-party installation command
Risk Level: MediumVulnerable Code Snippet:
markdown > **[SEO & GEO Skills Library](https://skills.sh/aaron-he-zhu/seo-geo-claude-skills)** · 20 skills for SEO + GEO · Install all: `npx skills add aaron-he-zhu/seo-geo-claude-skills`Technical Analysis
The documentation recommends executing
npx skillswithout pinning the CLI package to a reviewed version. It also identifies the skill collection by a mutable package name rather than an immutable version or commit. Depending on the localnpxand package-manager configuration, the command may retrieve and execute the latest available CLI package.Consequently, the code that ultimately runs or the skills that are installed can change after this project has been audited. Compromise of the relevant package, publisher account, registry distribution path, or a later upstream release could convert the documented command into a code-execution or malicious-skill delivery channel.
The audited project does not automatically execute this command, and no malicious payload was present in the reviewed files. Exploitation requires a user or automation system to follow the installation instruction.
Attack Path
- An attacker compromises the publisher account, upstream package, distribution channel, or a future release associated with the unpinned CLI or skill collection.
- The attacker publishes a modified package or skill release containing malicious installation or runtime behavior.
- A user follows the command documented at
SKILL.md:35. npxresolves and retrieves the mutable package version available at execution time.- The retrieved CLI executes, or it installs attacker-controlled skills.
- The malicious component operates with the permissions of the user or automation account that invo ...[truncated 734 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsCLI to a specific reviewed version, rather than allowingnpxto resolve the latest release. - Pin the requested skill collection to a supported immutable version or commit hash if the installer permits it.
- Document the expected package registry and upstream repository so users can verify package provenance.
- Publish and verify cryptographic checksums or signatures for downloaded artifacts.
- Use
npxoptions that prohibit silent substitution or unexpected package installation where supported. - Prefer a reviewed lockfile-based or locally vendored installation process for security-sensitive environments.
- Run installation under a least-privileged account without access to production credentials.
- Review package lifecycle scripts and installed skill contents before enabling them.
- Add automated dependency monitoring so pinned versions can be deliberately reviewed and updated when security fixes are released.
- Pin the
