T08 · Insecure Dependencies
- Location
SKILL.md:222- Finding
Unpinned and Unverified Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 222
Vulnerability Type: Insecure third-party dependency installation
Risk Level: MediumComplete Code Snippet:
markdown | Q1 | 如何安装agent-research？ | 请确保您的系统满足最低要求，然后通过pip安装：`pip install agent-research` |Technical Analysis
The documentation instructs users to install
agent-researchfrom the Python package index configured in their environment. The command does not pin an exact version, verify a package hash, identify a trusted publisher, or reference reviewable source code.Because this project contains only
SKILL.mdand no implementation, the externally resolved package would provide the executable behavior. Its contents may differ from the audited Skill and may change over time. This creates a supply-chain exposure through package compromise, an unsafe configured index, package-name takeover, or installation of an unexpectedly modified release.Python packages may execute package-controlled code during installation or later when imported and run. Consequently, following this instruction crosses the boundary from reviewed documentation to unreviewed executable code.
Attack Path
- An attacker compromises or takes control of the package, one of its dependencies, or a package index used by the target environment.
- The attacker publishes a malicious package version under the expected name or manipulates dependency resolution.
- A user follows the documented instruction and runs
pip install agent-research. pipresolves and installs the attacker-controlled package because no exact version or integrity hash is required.- Malicious code executes during installation or when the installed package is subsequently imported or invoked.
Impact Assessment
Malicious package code could execute with the privileges of the user running
pip. Depending on those privileges and the environment, this could permit access to projec ...[truncated 446 chars]- Remediation
View remediation
Remediation Suggestions
- Remove the installation instruction unless the package identity, ownership, and source can be independently verified.
- Pin the dependency to a reviewed exact version, for example
agent-research==X.Y.Z. - Distribute and verify cryptographic hashes, using a locked requirements file and
pip install --require-hashes. - Document the trusted package index and verified publisher or official source repository.
- Review the package and its complete transitive dependency tree before recommending installation.
- Install into an isolated virtual environment or sandbox under a non-privileged account.
- Avoid administrator or root installation and restrict access to credentials and sensitive files during package installation and execution.
- Use a controlled internal package mirror and automated dependency scanning where appropriate.