T08 · Insecure Dependencies
- Location
SKILL.md:51- Finding
Unpinned Third-Party Package Execution via npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 51
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code:
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 documented installation command invokes
npx skillswithout pinning theskillspackage to a reviewed version or verifying package integrity. Depending on npm and local cache behavior,npxcan retrieve the currently resolved package from the configured registry and execute its command-line entry point.Consequently, the code executed when a user follows this instruction may differ from the code available when this Skill was audited. This creates a supply-chain trust boundary outside the reviewed project. Exploitation would require compromise or malicious control of the resolved package, its publisher account, the package registry path, or a transitive dependency. The audited repository itself does not contain an active malicious payload.
Attack Path
- An attacker compromises the resolved
skillspackage, its publisher account, its dependency chain, or a relevant package-distribution path. - The attacker publishes a malicious version or modifies a dependency used during command execution.
- A user follows the installation instruction in
SKILL.md. npxresolves and downloads the mutable third-party package without an explicit version or integrity constraint.- The package's command-line entry point executes with the permissions and environment of the invoking user.
- Malicious installation logic could access files and credentials available to that user, alter the workspace, or execute additional commands.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the invoking user's account. The accessible scop ...[truncated 424 chars]
- An attacker compromises the resolved
- Remediation
View remediation
Remediation Suggestions
- Pin the command-line package to a specifically reviewed version, for example by using an explicit
package@versionreference. - Prefer a committed lockfile and an installation mechanism that enforces locked dependency versions.
- Verify package integrity using trusted checksums, signatures, or registry integrity metadata before execution.
- Document the expected package registry, publisher identity, package name, and reviewed version so users can detect substitutions.
- Disable or avoid automatic execution of newly downloaded packages where practical. Install the verified package first, inspect its provenance, and invoke the installed binary separately.
- Review transitive dependencies and use automated dependency monitoring for later security advisories or unexpected ownership changes.
- Warn users not to run the installation command with administrator or root privileges and to use an isolated environment with minimal credentials and filesystem access.
- Pin the command-line package to a specifically reviewed version, for example by using an explicit