T08 · Insecure Dependencies
- Location
SKILL.md:103- Finding
Unverified and Unpinned Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:103
Vulnerability Type: Untrusted dependency installation and supply-chain exposure
Risk Level: HighComplete vulnerable snippet:
markdown - **Dependency installation command**: `pip install arb-engine`Technical Analysis
The skill directs the user or agent to install the external
arb-enginePython package without specifying an exact version, package hash, authoritative package index, or verified publisher. The package source is not included in the audited project, so its installation scripts and runtime behavior cannot be reviewed.An unpinned installation resolves whichever release the configured package index currently considers appropriate. A compromised publisher account, malicious release, dependency-confusion condition, or unsafe package index could therefore cause attacker-controlled code to be installed. Python packages may execute code during build or installation, and arbitrary package code executes when imported or invoked.
The project also declares the
exectool, increasing the likelihood that an agent could perform the installation directly rather than merely displaying the command.Attack Path
- A user or agent follows the dependency installation instructions.
pipresolvesarb-engineusing the environment's configured package index.- A malicious or compromised release is selected because no trusted version or cryptographic hash is required.
- Attacker-controlled build, installation, import, or runtime logic executes on the local system.
- The malicious package operates with the permissions of the invoking user and may access files, environment variables, API credentials, or network resources available to that account.
Impact Assessment
Successful exploitation can result in arbitrary code execution with the privileges of the user running
pipor the agent. The accessible scope may include the current ...[truncated 472 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an explicitly reviewed version, such as
arb-engine==X.Y.Z. - Publish the authoritative package repository, publisher identity, and expected package index.
- Generate and verify cryptographic hashes through a locked requirements file and
pip install --require-hashes. - Review the package source, build configuration, transitive dependencies, and installation hooks before recommending execution.
- Prefer an isolated virtual environment or sandbox with no production credentials.
- Prevent autonomous installation unless the user explicitly approves the exact package, version, source, and hash.
- Include the required implementation in the audited project or provide reproducible build and provenance documentation.
- Pin the dependency to an explicitly reviewed version, such as
