T08 · Insecure Dependencies
- Location
SKILL.md:212- Finding
Third-Party SDK Installation Without Integrity Verification
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 212 and 229
Vulnerability Type: Supply-chain exposure through third-party package installation
Risk Level: MediumVulnerable Code Snippet
bash pip install scavio==0.15.0bash npm install scavio@0.15.0Technical Analysis
The Skill recommends installing Python and JavaScript SDKs from public package registries. Although both dependencies are pinned to version
0.15.0, the instructions do not provide cryptographic hashes, lockfiles, package provenance, or source-verification procedures.Version pinning prevents unintended upgrades but does not protect against a compromised publisher account, malicious package release, registry compromise, or package artifact replacement. Python package installation may execute build-system code, while npm packages may execute lifecycle scripts during installation. Imported SDK code also executes within the calling agent's process.
The SDKs are not strictly necessary for the declared functionality because
SKILL.mdalready documents direct HTTPS requests to the Scavio API. Consequently, installing executable third-party code increases the Skill's local privilege and supply-chain exposure beyond the minimum required for API access.There is no evidence in the reviewed project that
scavio==0.15.0orscavio@0.15.0is currently malicious. The finding concerns the unverified installation workflow and resulting trust boundary.Attack Path
- An attacker compromises the relevant package publisher account, registry infrastructure, or pinned package artifact.
- The attacker introduces malicious installation, build, lifecycle, or runtime code into version
0.15.0. - A user follows the Skill instructions and installs the affected package.
- Malicious code executes during package installation or when the SDK is imported.
- The code runs with the installing user's privileges and may access ...[truncated 866 chars]
- Remediation
View remediation
Remediation Suggestions
- Prefer the documented direct HTTPS API workflow, which avoids executing an optional SDK locally.
- If SDK use is retained, provide lockfiles and verify package artifacts using cryptographic hashes or registry integrity metadata.
- Publish links to the authoritative source repositories and document a process for verifying package provenance and release signatures.
- For Python, use hash-locked requirements such as
pip install --require-hashes -r requirements.txt. - For npm, commit a reviewed lockfile, use
npm ci, and consider--ignore-scriptswhen lifecycle scripts are unnecessary. - Install dependencies inside a sandboxed virtual environment or container with minimal filesystem, secret, and network access.
- Do not expose
SCAVIO_API_KEYor unrelated credentials during package installation. - Perform dependency scanning and package-content review before approving future SDK versions.
