T08 · Insecure Dependencies
- Location
README.md:6- Finding
Unpinned Third-Party Installation Command Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
README.md:6
Vulnerability Type: Unpinned third-party executable and mutable Skill source
Risk Level: MediumVulnerable Code:
bash npx skills add shuliuzhenhua-sys/google-serper-searchTechnical Analysis
The documented installation command invokes the
skillsnpm executable throughnpxwithout specifying a reviewed version. Depending on the local npm environment,npxcan retrieve and execute the latest available version of that package. The command also identifies the Skill through a mutable repository-style reference rather than an immutable commit, signed release, or verified artifact.Consequently, the code executed or installed when a user follows the documentation can differ from the version covered by this audit. Compromise of the npm package, package maintainer account, upstream Skill repository, or release process could cause users to receive malicious installation logic or modified Skill content.
No malicious dependency or active compromise was identified in the audited files. The vulnerability is the absence of version and integrity controls at the documented supply-chain boundary.
Attack Path
- An attacker compromises the npm package, its publisher account, the referenced Skill source, or another relevant upstream distribution channel.
- The attacker publishes a malicious version of the
skillsexecutable or replaces the mutable Skill content. - A user follows the documented
npx skills add shuliuzhenhua-sys/google-serper-searchcommand. npxobtains and executes the unreviewed package version, or the installer obtains the modified Skill.- The malicious installer or Skill executes with the invoking user's privileges or is installed into the user's agent environment.
- The compromised content can then affect installation-time operations or later agent sessions in which the Skill is loaded.
Impact Assessment
Explo ...[truncated 604 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm CLI to an explicitly reviewed version, for example by using a version-qualified package reference supported by npm.
- Pin the Skill source to an immutable commit hash or a specific, verified release rather than a mutable repository reference.
- Publish and verify cryptographic checksums or signatures for distributed artifacts.
- Commit and enforce an npm lockfile where package-based installation is part of a maintained installation workflow.
- Use npm provenance and package-signature verification where available.
- Document the exact expected package version, source revision, checksum, and verification procedure.
- Advise users not to run the installer with administrative privileges and to review installation scripts before execution.
- Periodically re-audit pinned dependency updates before changing the documented versions.
