T08 · Insecure Dependencies
- Location
SKILL.md:231- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 231
Vulnerability Type: Unpinned and mutable third-party dependencies
Risk Level: MediumVulnerable Code
text **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 installation instructions retrieve third-party components without pinning an exact reviewed version or validating an integrity hash. In particular,
pip install -U cellcogintentionally selects the latest available package release, while thenpxand OpenClaw installation commands similarly reference mutable upstream package or repository state.The project does not include a lockfile, package hashes, vendored dependency source, or another mechanism that binds installation to the implementation reviewed during this audit. Consequently, the effective code installed by these commands can change after the skill has been reviewed. Package installation hooks and subsequently imported SDK code may execute with the privileges of the user running the agent.
Attack Path
- An attacker compromises an upstream package publisher, registry account, repository, release process, or transitive dependency.
- The attacker publishes a malicious version under a dependency name referenced by the documented installation commands.
- A user follows the instructions in
SKILL.mdwithout an exact version or integrity constraint. - The package manager resolves and downloads the attacker-controlled release.
- Malicious installation hooks or runtime package code execute in the user's environment when the package is installed or imported.
This attack path d ...[truncated 644 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin every dependency to an exact version that has undergone security review.
- Use lockfiles and cryptographic integrity hashes where supported, such as hash-checked Python requirements.
- Document and verify the canonical registry, publisher, and repository for each package.
- Avoid automatic upgrades such as
pip install -Uin security-sensitive installation guidance. - Review dependency source code and release provenance before approving version updates.
- Disable package installation scripts where feasible and perform installation in a restricted environment.
- Run the SDK with least privilege and expose only the credentials and files required for the task.
- Use automated dependency monitoring and require explicit review before updating pinned versions.
