T08 · Insecure Dependencies
- Location
SKILL.md:158- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 158-161
Vulnerability Type: Supply-chain risk from mutable, unverified third-party dependencies
Risk Level: MediumThe skill recommends installing CellCog packages and skill content from external registries without pinning an exact version or immutable revision and without verifying a checksum or signature.
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
These installation commands resolve mutable third-party content at installation time. No exact package version, immutable source revision, lockfile, checksum, or signature is specified. In particular,
pip install -U cellcogexplicitly requests an available upgraded release rather than a reviewed version.The installed package, skill content, and transitive dependencies are not included in this project and therefore were outside the reviewed artifact. If an upstream registry account, repository, release process, or transitive dependency is compromised, following these instructions could introduce attacker-controlled code after this skill has passed review.
This finding does not establish that the current CellCog package is malicious. It identifies an unsafe dependency acquisition process that does not guarantee users receive the same dependency content that was reviewed or tested.
Attack Path
- An attacker compromises an upstream package publisher, skill repository, registry account, or transitive dependency.
- The attacker publishes a malicious release under the dependency name referenced by the documented commands.
- A user follows the i ...[truncated 1061 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every dependency to a reviewed exact version rather than installing the latest available release.
- Where Git-based skill installation is required, reference an immutable commit hash instead of a mutable branch or tag.
- Publish expected cryptographic checksums or verified signatures for downloaded artifacts and require validation before installation.
- Use lockfiles or equivalent dependency manifests that pin all transitive dependencies.
- Avoid
pip install -Uin security-sensitive setup instructions; use an exact version such ascellcog==<reviewed-version>. - Restrict installation to documented trusted registries and enable package provenance or signature verification where supported.
- Run installation and execution in a least-privilege virtual environment or sandbox without unnecessary secrets.
- Review and test each dependency update before changing the pinned version, including inspecting installation hooks and transitive dependency changes.
