T08 · Insecure Dependencies
- Location
SKILL.md:93- Finding
Unpinned Third-Party Executable Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 93–96; dependency instruction repeated at line 302
Vulnerability Type: Unpinned third-party package installation
Risk Level: MediumVulnerable code:
bash pip install md-exporter # ... # Or install through uv uv tool install md-exporterThe dependency table repeats the installation instruction:
markdown | md-exporter | Python package | Required | `pip install md-exporter` |Technical Analysis
The Skill instructs the Agent to install and execute the
md-exporterpackage without specifying an exact version, verifying package hashes, identifying a trusted publisher or repository, or using a lock file. Package names alone resolve to mutable artifacts from the configured Python package index.Consequently, the code reviewed during one installation may differ from the package retrieved later. If the package, publisher account, registry, or dependency chain is compromised, installation hooks or the subsequently invoked
markdown-exporterexecutable could run attacker-controlled code. The project contains no local implementation that would allow the installed package's behavior to be independently audited.This finding identifies an unsafe supply-chain configuration; the available evidence does not establish that the current
md-exporterpackage is malicious.Attack Path
- An attacker publishes or introduces a malicious release through compromise of the package, publisher account, registry, or transitive dependency chain.
- An Agent follows
SKILL.mdand runspip install md-exporteroruv tool install md-exporter. - The package manager resolves the mutable package name to the attacker-controlled release because no exact version or integrity hash is required.
- Package-controlled code executes during installation or when the Agent invokes the documented
markdown-exportercommands. - The malicious code opera ...[truncated 796 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
md-exporterto an exact, independently reviewed version rather than installing the latest available release. - Use a hash-locked requirements file or equivalent lock mechanism, such as:
text md-exporter==REVIEWED_VERSION \ --hash=sha256:VERIFIED_DISTRIBUTION_HASH - Document the package's canonical repository, expected publisher, and verification process.
- Review and lock all transitive dependencies, not only the top-level package.
- Retrieve packages from a trusted, controlled index or an internally mirrored artifact repository.
- Run installation and document conversion in an isolated environment with least-privilege filesystem access and restricted network access.
- Prevent the converter from accessing credentials, unrelated user files, and sensitive environment variables.
- Add automated dependency provenance, integrity, and vulnerability checks before approving package updates.
- Pin
