T08 · Insecure Dependencies
- Location
SKILL.md:57- Finding
Unverifiable External Repository and Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 57–63
Vulnerability Type: Untrusted external source and insecure dependency installation
Risk Level: MediumVulnerable Code
bash git clone <YOUR_REPO_URL> paper2diagram-agent cd paper2diagram-agent python3 -m venv .venv source .venv/bin/activate pip install -r requirements.txt cp .env.example .env # 按需填入 KEYTechnical Analysis
The supplied project contains only
SKILL.md; it does not include the advertised Python workflow,requirements.txt, dependency lockfile, or integrity metadata. The installation instructions direct users to replace an unspecified repository placeholder and install dependencies defined by that external repository.Consequently, the executable implementation and its dependency graph are outside the reviewed artifact and can change independently after this Skill is audited. In addition, Python package installation may execute package-controlled build hooks or installation logic. No dependency versions or cryptographic hashes are provided to ensure that users receive reviewed package contents.
This finding does not establish that a particular repository or package is malicious. The risk arises because the documentation establishes an unverified supply-chain path through which substituted, compromised, dependency-confused, or otherwise malicious components could be installed and executed.
Attack Path
- A user or agent follows the deployment instructions in
SKILL.md. - An attacker supplies a malicious value for
YOUR_REPO_URL, compromises the selected repository, or introduces a malicious dependency through itsrequirements.txt. - The user clones the repository without verifying its owner, commit, signature, or content.
- The user executes
pip install -r requirements.txt. - A malicious dependency executes code through package build or installation mechanisms, or the cloned workflow exe ...[truncated 1012 chars]
- A user or agent follows the deployment instructions in
- Remediation
View remediation
Remediation Suggestions
- Include the complete workflow implementation, dependency manifest, and relevant configuration in the auditable Skill package.
- Replace
YOUR_REPO_URLwith a specific official repository hosted under a verified project organization. - Pin installation instructions to a reviewed immutable commit or signed release rather than a mutable branch.
- Provide a lockfile containing exact dependency versions and cryptographic hashes. Use hash-enforced installation, such as
pip install --require-hashes. - Review direct and transitive dependencies for dependency confusion, typosquatting, known vulnerabilities, and unexpected build scripts.
- Publish checksums or signatures for releases and document how users must verify them before installation.
- Run installation and document processing inside an isolated, least-privileged environment with restricted filesystem and network access.
- Do not expose API keys to package installation processes. Provide credentials only to the runtime process after dependencies and source contents have been verified.
- Add automated dependency scanning, provenance verification, and reproducible-build checks to the release process.
