T08 · Insecure Dependencies
- Location
SKILL.md:50- Finding
Unpinned Third-Party Dependencies Create a Mutable Software Supply Chain
- Content
View full analysis
Vulnerability Details
File Locations:
SKILL.md:50README.md:24
Vulnerability Type: Unpinned and unverifiable third-party dependencies
Risk Level: MediumAffected code snippets:
SKILL.md:50bash pip install langgraph langchain-openai feishu-oapiREADME.md:24bash pip install pyyamlTechnical Analysis
The installation instructions retrieve mutable package versions from the configured Python package index without version constraints, integrity hashes, or a reviewed lockfile. As a result, the code installed by these commands can differ from the code available when the Skill was audited.
Python package installation can execute package build and installation logic. A compromised upstream release, dependency takeover, malicious transitive dependency, or unsafe package-index configuration could therefore result in arbitrary code execution during installation or later import.
The risk is increased by the discrepancy between the supplied implementation and the dependencies requested in
SKILL.md. The audited code directly uses PyYAML, but the documentedlanggraph,langchain-openai, andfeishu-oapiintegrations are not implemented in the supplied project. These unnecessary dependencies expand the supply-chain attack surface without supporting current functionality.No evidence was found that the currently named packages are malicious. The vulnerability is the absence of reproducible version and integrity controls.
Attack Path
- A user follows the documented installation instructions.
pipresolves the latest compatible versions from the user's configured package index.- An upstream package, transitive dependency, or configured package source supplies a compromised release.
- Malicious build or installation logic executes during
pip install, or malicious package code executes when imported. - The payload runs with t ...[truncated 695 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
langgraph,langchain-openai, andfeishu-oapifrom the installation instructions unless the corresponding integrations are implemented and required. - Pin every direct dependency to an explicitly reviewed version.
- Resolve and lock transitive dependencies using a reproducible dependency-management process.
- Generate and verify cryptographic hashes, such as by installing from a hash-locked requirements file with
pip install --require-hashes. - Use a trusted, explicitly configured package index and prevent unintended fallback to untrusted indexes.
- Install dependencies in an isolated virtual environment under a non-privileged account.
- Keep
README.md,SKILL.md, Skill metadata, and the actual implementation synchronized so users install only dependencies required by the shipped code. - Add automated dependency scanning and periodic review of pinned package versions.
- Remove
