T08 · Insecure Dependencies
- Location
README.md:15- Finding
Unpinned Third-Party Installation with Global Scope
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 15-17
Vulnerability Type: Unpinned third-party package execution and global installation
Risk Level: MediumVulnerable Code
bash npx skills add xie-jun/zhang-yiming-perspective -gTechnical Analysis
The documented installation procedure invokes the third-party
skillspackage throughnpxwithout specifying an immutable package version. It also identifies the Skill repository through a mutable owner/name reference rather than a fixed commit hash and requests global installation through the-goption.When executed,
npxmay retrieve and run the package version currently available from the configured npm registry. Consequently, the code executed at installation time can differ from the version reviewed during this audit. No lockfile, package integrity hash, repository commit, or signature is provided to authenticate the retrieved components.There is no evidence in the audited project that the current package or repository is malicious. The vulnerability is the unsafe trust model of the documented installation process, which exposes users to package compromise, account takeover, malicious publication, or an upstream supply-chain incident.
Attack Path
- An attacker compromises the npm account or registry entry associated with the unpinned
skillspackage, or compromises the mutable repository referenced byxie-jun/zhang-yiming-perspective. - The attacker publishes a modified package version or replaces repository content with malicious installer logic.
- A user follows the README and executes:
bash npx skills add xie-jun/zhang-yiming-perspective -g npxretrieves and executes the currently published package rather than a previously reviewed immutable version.- The malicious installer runs with the permissions of the invoking user and performs a global installation.
- Attacker-controlled files, Skill instructions, or executable hooks ...[truncated 1007 chars]
- An attacker compromises the npm account or registry entry associated with the unpinned
- Remediation
View remediation
Remediation Suggestions
-
Prefer the platform-native installation command already documented by the project:
bash clawhub install zhang-yiming-perspective -
If the
npxinstallation method must remain, pin the CLI to a reviewed version:bash npx skills@<reviewed-version> add xie-jun/zhang-yiming-perspective@<immutable-commit> -
Replace mutable branch or repository references with an immutable commit hash or signed release tag.
-
Publish and verify cryptographic integrity information, such as package integrity hashes, checksums, or signed release attestations.
-
Remove
-gunless global installation is strictly required. Prefer project-local or user-scoped installation to limit the affected scope. -
Document the expected package source, version, publisher identity, and verification procedure so users can detect registry substitution or account compromise.
-
Add automated dependency and release provenance checks, including package signature verification and monitoring for unauthorized package-version changes.
-
