T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Third-Party Executable Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 17
Vulnerability Type: Unpinned third-party package installation
Risk Level: MediumVulnerable Code
markdown If neither is available, install the package: `pip install kannaka-quantum` (or `pip install -e .` from the repo). Python ≥ 3.10. If a spawned process can't find Python, set `KANNAKA_QUANTUM_PYTHON` to the interpreter path.Technical Analysis
The skill instructs the agent to install and execute
kannaka-quantumfrom pip without specifying an audited version, package hash, lockfile, or trusted package index. Consequently, the code installed at execution time may differ from the code that existed when the skill was reviewed.The project contains only
SKILL.md; it does not include the package implementation needed to verify the dependency's installation hooks, runtime behavior, network operations, credential handling, or command execution. Although the audit found no evidence that the named package is malicious, relying on an unpinned executable dependency creates a supply-chain weakness.The documented package is expected to interact with qBraid and OpenQuantum credentials and can manage paid compute and SSH-based remote agents. A compromised or unexpectedly changed package release would therefore execute in a security-sensitive context.
Attack Path
- The skill is invoked in an environment where the
kannaka-quantumMCP server and CLI are unavailable. - Following
SKILL.md, the agent runspip install kannaka-quantum. - pip resolves the current package release from its configured index rather than a reviewed, immutable artifact.
- An attacker who has compromised the package, its publisher account, the package index, or the dependency-resolution path supplies malicious installation or runtime code.
- The code executes with the permissions of the user running pip or the installed CLI.
- When the CLI is subsequently used, malicious code may access crede ...[truncated 891 chars]
- The skill is invoked in an environment where the
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a specifically reviewed version, for example with an exact
==constraint. - Require cryptographic hashes through a locked requirements file and install with
pip install --require-hashes. - State the canonical package repository and trusted package index explicitly.
- Review the pinned package and its complete transitive dependency graph before deployment.
- Install the dependency in an isolated virtual environment or container under a non-privileged account.
- Disable unnecessary access to local credential files and environment variables during installation.
- Use narrowly scoped, short-lived qBraid and OpenQuantum credentials at runtime.
- Separate package installation from authenticated execution so installation hooks cannot access production credentials.
- Prefer bundled, reviewable source or a verified immutable artifact when practical.
- Add dependency-integrity monitoring and require manual review before updating the pinned version.
- Pin the dependency to a specifically reviewed version, for example with an exact
