T08 · Insecure Dependencies
- Location
requirements.txt:1- Finding
Unsafe and Inconsistent Package Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
requirements.txt:1-2,README.md:18-20,SKILL.md:86-89,package.json:2
Vulnerability Type: Dependency confusion and installation of an unverified package namespace
Risk Level: MediumVulnerable Code
requirements.txt:1-2:text # Core Dependencies python>=3.8README.md:18-20:bash git clone https://github.com/agent-security/scanner.git cd scanner pip install -r requirements.txtSKILL.md:86-89:bash npm install -g asc-scanpackage.json:2:json "name": "agent-security-scanner",Technical Analysis
python>=3.8is placed inrequirements.txtas though the Python interpreter were an installable PyPI dependency. Python dependency files are intended to list distribution packages, not interpreter-version constraints. A package manager can therefore attempt to resolve and install a third-party distribution namedpython, which is unrelated to enforcing the required interpreter version.The npm installation documentation also instructs users to globally install
asc-scan, while the supplied package metadata declares the package name asagent-security-scanner. The documentation states that npm publication is pending, and the audited artifact provides no evidence that theasc-scannamespace is controlled by this project.These inconsistencies create a supply-chain exposure: users may retrieve code from an unintended package namespace rather than installing the audited project.
Attack Path
- An attacker publishes, controls, or compromises the package namespace referenced by the documentation, such as
asc-scanor the unintended PyPI distributionpython. - A user follows the project's documented installation procedure.
- The package manager resolves the external package from the public registry.
- Package installation or lifecycle code executes under the privileges of the in ...[truncated 1234 chars]
- An attacker publishes, controls, or compromises the package namespace referenced by the documentation, such as
- Remediation
View remediation
Remediation Suggestions
- Remove
python>=3.8fromrequirements.txt. - Enforce the interpreter version through appropriate packaging metadata, such as:
toml [project] requires-python = ">=3.8" - Use one consistent and verified npm package name across
package.json,SKILL.md, and all installation documentation. - Remove npm installation instructions until the package has been published under a namespace demonstrably controlled by the project.
- Pin release versions in installation examples rather than installing an unspecified latest version.
- Publish package checksums, signed release artifacts, and registry provenance information.
- Test installation in a clean virtual environment and CI environment to verify that no unrelated distributions are downloaded.
- Advise users not to install with elevated privileges and to use isolated Python virtual environments and an npm prefix owned by the user.
- Remove
