T08 · Insecure Dependencies
- Location
SKILL.md:11- Finding
Unpinned npm Dependency Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 11–14
Vulnerability Type: Unpinned third-party npm dependency
Risk Level: MediumVulnerable Code
yaml install: - kind: npm package: utifThe same unversioned dependency declaration also appears in
skill.md, lines 12–15:yaml install: - kind: npm package: utif bins: []In addition,
README.md, lines 19–20, recommends installing another package globally without a fixed version:bash npm install -g clawhub clawhub install tiff-mergeTechnical Analysis
The installation metadata identifies npm packages only by name and provides no exact version, lockfile, or integrity hash. Consequently, installation may resolve a mutable future release rather than the version that was reviewed.
This does not establish that either named package is currently malicious. It creates a supply-chain exposure: if a package or maintainer account is compromised, ownership changes, or a future release is malicious, users can receive code different from the audited dependency. npm package lifecycle code may execute during installation, while
utifis also loaded at runtime throughrequire('utif').Attack Path
- An attacker compromises a referenced npm package, its publisher account, or its release process.
- The attacker publishes a malicious release under the legitimate package name.
- A user installs the skill according to its metadata or documentation.
- Because no exact reviewed version is required, npm resolves the attacker-controlled release.
- Malicious package lifecycle code may execute during installation, or malicious runtime code may execute when
index.jsloads and uses the dependency.
This exploitation path depends on upstream package or publisher compromise; the audited project itself contains no remote payload retrieval or malicious code.
Impact Assessment
Malicious de ...[truncated 642 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every dependency to an exact, reviewed version rather than a package name or floating range.
- Add a package manifest and committed lockfile containing registry integrity hashes.
- Use deterministic installation, such as
npm ci, where supported. - Pin the ClawHub CLI version in installation documentation and avoid global installation unless it is operationally necessary.
- Review package provenance, publisher ownership, lifecycle scripts, and release changes before updating pinned versions.
- Run installation and image processing under a least-privileged account, without unnecessary access to secrets or sensitive directories.
- Consider disabling npm lifecycle scripts during installation when dependencies do not require them.
