T08 · Insecure Dependencies
- Location
README.md:39- Finding
Unpinned External Executable Dependencies
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 39 and 42–45
Vulnerability Type: Supply-chain exposure through unpinned external packages and mutable source repositories
Risk Level: MediumVulnerable Code Snippet
bash pip install visual-bug-hunterbash git clone https://github.com/yitao2027/visual-bug-hunter.git cd visual-bug-hunter pip install -e .Technical Analysis
The documented installation methods retrieve and execute Python packaging code from external sources without pinning an exact package version, immutable commit, cryptographic hash, or signature.
The PyPI package and GitHub implementation are not included in the audited artifact, which contains only
README.mdandSKILL.md. Consequently, the audit cannot verify package build hooks, transitive dependencies, runtime network behavior, filesystem access, screenshot processing, subprocess use, or other executable behavior.The GitHub command clones the repository's default branch, whose contents can change after this Skill has been reviewed. The unversioned PyPI command likewise installs whichever release the package index currently resolves. During installation, Python build backends and package setup hooks may execute code with the installing user's privileges.
This is a supply-chain weakness rather than evidence that the currently referenced package is malicious.
Attack Path
- An attacker compromises the referenced PyPI project, a maintainer account, the GitHub repository, or a relevant dependency.
- The attacker publishes a modified package release or changes the repository's default branch.
- A user follows one of the documented installation procedures.
pipdownloads and processes attacker-controlled package metadata, build configuration, dependencies, or installation hooks.- Malicious code executes with the user's privileges during installation or later when the installed CLI is invoked.
- The payload may access resources ava ...[truncated 771 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the PyPI dependency to a reviewed, exact version rather than installing the latest available release.
- Generate a locked dependency set and require cryptographic hashes, such as through
pip --require-hashes. - Pin source installations to a reviewed immutable commit instead of cloning a mutable default branch.
- Publish and verify signed releases, attestations, checksums, and build provenance.
- Include the executable implementation in the audited artifact so its installation hooks, dependencies, and runtime behavior can be reviewed.
- Review and pin all transitive dependencies, not only the top-level package.
- Install the tool in an isolated, least-privileged environment and grant screen capture or accessibility permissions only when required.
- Ensure the executable implementation technically enforces the project-directory and target-process restrictions declared in
SKILL.md.
