T08 · Insecure Dependencies
- Location
README.md:97- Finding
Unpinned npx Package Execution in Installation Guidance
- Content
View full analysis
Vulnerability Details
File Locations:
README.md:97andREADME.fr.md:77
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
README.md:97:markdown | skills.sh / ClawHub | [`SKILL.md`](SKILL.md) (`npx skills add Anymfah/stellary-mcp`) |README.fr.md:77contains the equivalent command:markdown | skills.sh / ClawHub | [`SKILL.md`](SKILL.md) (`npx skills add Anymfah/stellary-mcp`) |Technical Analysis
The documented command invokes the unversioned
skillspackage throughnpx. If the package is not already installed locally,npxmay retrieve its current release from the configured npm registry and execute it immediately.Because neither a reviewed package version nor an integrity value is specified, the code executed by this installation command can change after this repository has been audited. This creates a mutable supply-chain trust boundary: compromise of the package, its publisher account, or the package-resolution source could cause users to execute code that was not part of this reviewed project.
The repository's own
package.jsonhas no third-party dependencies or lifecycle hooks, so this risk is limited to users who follow the documented installation command. No evidence indicates that the currentskillspackage is malicious.Attack Path
- An attacker compromises the publishing account, registry entry, or distribution path for the package resolved as
skills. - The attacker publishes a modified release containing malicious executable behavior or lifecycle scripts.
- A user follows the documented
npx skills add Anymfah/stellary-mcpcommand. npxresolves and downloads the mutable package release.- The downloaded package executes with the privileges and environment of the invoking user.
- Malicious code could access files, environment variables, network resources, and credentials available to ...[truncated 764 chars]
- An attacker compromises the publishing account, registry entry, or distribution path for the package resolved as
- Remediation
View remediation
Remediation Suggestions
-
Pin the installer to a specific reviewed version, for example:
bash npx --yes skills@<reviewed-version> add Anymfah/stellary-mcp -
Verify that the pinned version is obtained from the intended publisher and registry before documenting it.
-
Where tooling permits, enforce package integrity using a lockfile, checksum, signed provenance, or equivalent verification.
-
Update both
README.mdandREADME.fr.mdso that all installation instructions use the same pinned and reviewed release. -
Document that users must not run the installation command with
sudoor another elevated account. -
Prefer a non-executing manual installation procedure when practical, such as copying the reviewed
SKILL.mdand manifest files into the client configuration. -
Establish a release process that explicitly reviews and updates the pinned installer version rather than automatically tracking the latest package.
-
