T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Installation of an Unverified and Unpinned Third-Party npm Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 8
Vulnerability Type: Third-party supply-chain risk
Risk Level: MediumComplete Code Snippet:
text npm install @self-evolving-harness/claw-designTechnical Analysis
The skill instructs users to install
@self-evolving-harness/claw-designdirectly from the npm registry. The dependency is not pinned to an exact version, no integrity hash or lockfile is supplied, and the dependency source is not included in the audited project. Consequently, the code ultimately installed can change independently after this skill has been reviewed.npm packages can define lifecycle scripts, such as
preinstall,install, andpostinstall, which may execute automatically during installation. The package implementation and lifecycle behavior could not be verified from the provided project. The referenced GitHub repository also does not, by itself, prove ownership of or correspondence with the npm scope.Attack Path
- A user follows the installation instruction in
SKILL.md. - npm resolves the current package version from the external registry.
- An attacker who has compromised the package, its publisher account, or its release pipeline publishes a malicious version.
- npm downloads that mutable version and may execute its lifecycle scripts during installation.
- The malicious package executes with the operating-system permissions of the user running npm.
This path depends on compromise or malicious control of the external dependency; the audited file does not itself contain an embedded malicious payload.
Impact Assessment
A malicious dependency could execute arbitrary code under the installing user's privileges. Depending on those privileges and the host environment, this could expose accessible files, source code, environment variables, developer credentials, or authentication tokens. It could also modify project files, install additiona ...[truncated 170 chars]
- A user follows the installation instruction in
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a reviewed exact version rather than resolving the latest release.
- Provide and enforce a lockfile containing registry integrity metadata.
- Verify that the npm publisher and scope are legitimately associated with the referenced source repository.
- Audit the package source, transitive dependencies, release artifacts, and npm lifecycle scripts before recommending installation.
- Where practical, vendor the reviewed source or distribute a reproducibly built artifact with a documented cryptographic checksum.
- Perform the initial dependency retrieval with lifecycle scripts disabled, such as through an appropriate
--ignore-scriptsworkflow, and enable scripts only after review. - Install and test the package in a sandbox or minimally privileged environment without production credentials or sensitive files.
- Use dependency monitoring and publisher-account protections to detect compromised or unexpected releases.
