T08 · Insecure Dependencies
- Location
SKILL.md:28- Finding
Unpinned npm Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:28-31andREADME.md:6-10
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: MediumVulnerable Code
SKILL.md:28-31:markdown ## Install ```bash npx skills add blammectrappora/sticker-pack-skilltext `README.md:6-10`: ```markdown ## Install ```bash npx skills add blammectrappora/sticker-pack-skilltext ### Technical Analysis The documented installation command invokes the npm package named `skills` through `npx` without specifying a version or integrity constraint. If that package is not already installed locally, `npx` can retrieve its currently resolved release from the configured npm registry and execute its command. Consequently, the code executed during installation is not limited to the audited project. Its behavior can change independently after this skill has been reviewed. The repository provides no lockfile, package version, integrity hash, or verification procedure for the executable installer. This is a supply-chain weakness rather than evidence that the currently resolved package is malicious. ### Attack Path 1. An attacker compromises the publisher account or distribution pipeline for the npm package resolved as `skills`, or otherwise influences the registry used by the victim. 2. The attacker publishes a malicious release under the package/version that an unpinned `npx skills` command resolves. 3. A user follows the installation instructions. 4. `npx` downloads and executes the compromised package. 5. The package executes with the privileges of the user running the installation command. ### Impact Assessment Successful exploitation could provide arbitrary code execution under the installing user's account. Depending on that account's permissions, attacker code could read or modify user-accessible files, steal environment credentials, alter installed skills, or make outbound ...[truncated 169 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the installer to a reviewed, exact version, for example
npx --yes skills@X.Y.Z .... - Verify and document the official npm package scope, publisher, and registry.
- Use a lockfile and npm integrity metadata where the installation workflow permits it.
- Prefer a trusted, locally installed installer whose version is managed by the surrounding platform.
- Document a package-signature, checksum, or provenance-verification procedure before execution.
- Review new installer versions before updating the pinned version.
- Pin the installer to a reviewed, exact version, for example
