T08 · Insecure Dependencies
- Location
README.md:118- Finding
Unpinned Third-Party Installation Command
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 118-120
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
bash npx skills add ting2tao/jinjiancheng-skillTechnical Analysis
The documented installation command invokes the
skillsnpm CLI throughnpxwithout pinning the package version. It also installs the Skill from a mutable repository reference without specifying a release, tag, commit hash, checksum, or signature.Consequently, the code executed or installed when a user follows this instruction can differ from the content reviewed during this audit. A compromised npm package, maintainer account, repository, or mutable upstream branch could introduce malicious behavior after review.
Attack Path
- An attacker compromises the npm package, its publishing credentials, the referenced repository, or an associated maintainer account.
- The attacker publishes a malicious CLI version or modifies the repository's mutable default branch.
- A user follows the installation command from the README.
npxretrieves and executes the unpinned CLI, which then retrieves the mutable Skill content.- The malicious component executes or is installed under the privileges of the user running the command.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on the user's environment, this may expose source code, accessible credentials, configuration files, and other user-readable data. It could also modify files or install additional malicious components within that user's permission boundary.
The audited project itself contains no bundled executable scripts, credential access, persistence mechanism, destructive operation, or confirmed malicious payload. The risk arises from the mutable external installation chain rather than from embedded project code.
- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsnpm CLI to a reviewed, exact version rather than allowingnpxto resolve the latest release. - Pin the Skill source to an immutable commit hash or signed release instead of a mutable repository branch.
- Publish and document cryptographic checksums or signatures for release artifacts.
- Instruct users to verify the source revision and integrity metadata before installation.
- Use a locked dependency manifest where supported and review dependency changes before updating pinned versions.
- Avoid installation flows that execute newly downloaded package code automatically when a non-executing retrieval and verification step is available.
- Pin the
