T08 · Insecure Dependencies
- Location
README.md:63- Finding
Unpinned Third-Party Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:63-64
Vulnerability Type: Unpinned package execution and supply-chain exposure
Risk Level: MediumComplete Code Snippet:
bash **OpenClaw（通用安装器）** ```bash npx skills add CoolingRabbit/mattpocock-skills-kimitext ### Technical Analysis The installation guidance invokes the third-party `skills` package through `npx` without specifying an exact version, integrity hash, lockfile, or signature. If the package is unavailable locally, `npx` can retrieve and execute its currently resolved release from the configured npm registry. This makes the effective installer mutable after the audited repository has been reviewed. A compromised maintainer account, malicious package release, registry compromise, or unexpected upstream change could cause users to execute code that was not part of this audit. Package lifecycle scripts and installer logic would run with the privileges of the user performing the installation. The referenced repository name is an argument to the installer and does not constrain or authenticate the code of the `skills` package itself. ### Attack Path 1. An attacker compromises the npm package, its maintainer account, its publication workflow, or the registry resolution path. 2. The attacker publishes a malicious version that remains compatible with the documented command. 3. A user follows the README and runs `npx skills add CoolingRabbit/mattpocock-skills-kimi`. 4. `npx` resolves and downloads the mutable package version. 5. Malicious package lifecycle scripts or installer code execute under the installing user's account. 6. The payload can access resources available to that account and alter the Agent's Skill installation directories. ### Impact Assessment Successful exploitation could obtain code execution with the permissions of the user running `npx`. Depending on that user's environment, the maliciou ...[truncated 418 chars]- Remediation
View remediation
Remediation Suggestions
-
Pin the installer to an exact, reviewed package version, for example:
bash npx --yes skills@<audited-exact-version> add CoolingRabbit/mattpocock-skills-kimi -
Verify the package publisher and document the expected package registry and provenance.
-
Publish and verify package integrity or signatures where the distribution system supports them.
-
Review the pinned package's lifecycle scripts and transitive dependencies before recommending it.
-
Prefer installation from a verified repository commit or release archive rather than a mutable branch or package tag.
-
Document the expected commit SHA and provide checksum verification instructions.
-
Recommend running installation with least privilege and without unnecessary credentials in the environment.
-
Avoid executing the installer with
sudoor an administrative account.
-