T08 · Insecure Dependencies
- Location
SKILL.md:236- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 236-239
Vulnerability Type: Unpinned and unverified external dependencies
Risk Level: MediumVulnerable Code
markdown **Claude Code, Cursor, Codex + 70 more agents:** `npx skills add cellcog/skills --skill cellcog` **OpenClaw:** `openclaw skills install @cellcog/cellcog` **CellCog plugin users:** run `/cellcog-setup` (or `/cellcog:cellcog-setup` depending on your tool) **Manual setup:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.Technical Analysis
The Skill instructs users to obtain the CellCog dependency from external package or Skill distribution systems without specifying a reviewed version, immutable commit, checksum, or cryptographic signature. The
pip install -U cellcogcommand explicitly selects an available upgrade, while thenpxand OpenClaw installation commands similarly do not identify an immutable release.Consequently, the dependency installed at a future date may differ from the component that existed when this Skill was audited. The external dependency's implementation is not included in this project and therefore could not be assessed as part of the present audit. This creates a supply-chain trust boundary in which a compromised publisher account, package registry, upstream repository, or future malicious release could introduce attacker-controlled code.
This finding does not establish that the current CellCog package is malicious. The vulnerability is the absence of version and integrity controls around executable third-party dependencies.
Attack Path
- An attacker compromises the relevant upstream publisher account, repository, package registry entry, or release process.
- The attacker publishes a modified release under the expected CellCog package or Skill identifier.
- A user follows one of the documented unpinned installation commands.
- The packa ...[truncated 1248 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin CellCog to a specific reviewed version rather than selecting the latest available release.
- Where supported, reference an immutable commit hash or content-addressed package artifact.
- Publish and verify cryptographic hashes or signatures for downloaded artifacts.
- Use lockfiles with integrity metadata for package ecosystems that support them.
- Avoid implicit
npxresolution; specify an exact, reviewed package version. - Document the canonical package registry, publisher identity, and official repository so users can detect dependency-confusion or typosquatting attempts.
- Review dependency release notes and package contents before updating the pinned version.
- Install and run the dependency with least privilege in an isolated environment, exposing only the files and environment variables necessary for the task.
- Scope and rotate
CELLCOG_API_KEYcredentials where supported, and avoid forwarding unrelated secrets through prompts.
