T08 · Insecure Dependencies
- Location
SKILL.md:427- Finding
Unpinned Placeholder SDK Packages Create Dependency-Confusion Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 427–428
Vulnerability Type: Unverified and unpinned third-party dependencies
Risk Level: MediumVulnerable Code
bash pip install example-api-sdk # Python npm install example-api-sdk # JavaScriptTechnical Analysis
The Skill's generated quick-start template instructs users to install
example-api-sdkdirectly from public package registries. The apparent placeholder package name is presented as an executable command without an exact version, integrity verification, lockfile, provenance validation, or warning that it must be replaced with a verified package.The API-document generation function does not require installing an SDK. Including these commands therefore exceeds the minimum privileges and dependencies needed for the declared functionality.
Package installation can execute attacker-controlled setup or lifecycle scripts. If an attacker publishes, takes over, or compromises a package matching this generic name, users following the generated documentation may execute malicious code. The audit did not establish that the referenced packages are currently malicious; the vulnerability is the unsafe installation pattern and resulting dependency-confusion exposure.
Attack Path
- An attacker publishes or compromises a package named
example-api-sdkin the relevant Python or npm registry. - The Skill generates documentation containing the installation commands.
- A user copies and executes one of the commands without independently verifying the package.
- The package manager downloads the attacker-controlled package and executes any applicable installation or lifecycle hooks.
- The malicious package runs with the installing user's privileges and can access resources available to that account.
Impact Assessment
Successful exploitation may provide arbitrary code execution under the user's account. Depending on the en ...[truncated 437 chars]
- An attacker publishes or compromises a package named
- Remediation
View remediation
Remediation Suggestions
- Remove executable installation commands for placeholder packages.
- Do not require SDK installation for the core documentation-generation workflow.
- Replace placeholders only after identifying and validating the API provider's official package.
- Pin dependencies to reviewed exact versions rather than allowing automatic selection of the latest release.
- Use lockfiles and registry-supported integrity verification where available.
- Clearly label illustrative package names as non-executable placeholders.
- Require explicit user confirmation before recommending any third-party installation.
- Prefer generated standalone examples that use an already approved HTTP client instead of introducing a new SDK dependency.
