T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unpinned Global npm Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 18–22
Vulnerability Type: Supply-chain exposure through an unpinned third-party dependency
Risk Level: MediumVulnerable Code:
bash ## Prerequisites ```bash # Install and start the daemon npm install -g clawnexus clawnexus startTechnical Analysis
The skill instructs users to install the latest available release of the third-party
clawnexusnpm package globally without specifying an exact version, lockfile, integrity hash, or provenance verification procedure. Because npm package versions and distribution tags are mutable from the consumer's perspective, the installed code may differ from the version reviewed when this skill was published.npm installations can also execute package lifecycle scripts with the privileges of the invoking user. The instructions immediately start the newly installed daemon, further exposing the host to any malicious or unexpectedly changed behavior in the retrieved package.
Attack Path
- An attacker compromises the npm publisher account, publishing pipeline, or package distribution channel for
clawnexus. - The attacker publishes a malicious release or changes the package's latest distribution tag to point to one.
- A user follows the documented
npm install -g clawnexusinstruction. - npm retrieves the attacker-controlled release and may execute its lifecycle scripts with the user's privileges.
- The user runs
clawnexus start, executing and potentially persisting the malicious daemon. - The payload can access resources available to the user and interact with local or LAN services.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the privileges of the user running npm. The resulting scope may include reading or modifying user-accessible files, accessing environment data, interacting with local and LAN services, opening network listeners, or ...[truncated 242 chars]
- An attacker compromises the npm publisher account, publishing pipeline, or package distribution channel for
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an exact reviewed version, for example:
bash npm install -g clawnexus@0.4.0 - Verify that the pinned package version corresponds to the reviewed source revision and expected publisher.
- Publish and document package integrity and provenance verification, such as npm provenance attestations and a trusted checksum.
- Review package lifecycle scripts before recommending installation.
- Prefer a project-local or otherwise isolated installation over a global installation where operationally feasible.
- Avoid elevated privileges and document that the installation must not be run with
sudoor as an administrator. - Establish an explicit update and security-review process rather than automatically consuming the latest release.
- Pin the dependency to an exact reviewed version, for example:
