T08 · Insecure Dependencies
- Location
SKILL.md:83- Finding
Unverified Template Retrieval Followed by Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 83–96 and 122
Vulnerability Type: Supply-chain exposure through unverified templates and dependencies
Risk Level: MediumRelevant code snippets:
text 1. Template warmup // parallel with credential wait ← downloadTemplate + installmarkdown 1. **Warm template in parallel with credentials** (see partner notes below): `downloadTemplate` (`react` default, `vue` if requested) → `npm install` / `pnpm install`.markdown | WorkBuddy / connector without hooks | **Pre-enable** the CloudBase MCP connector for the tenant when possible; inject a short system brief that points here; warm `downloadTemplate` + `npm install` **during** credential/Trust wait (do not idle). |Technical Analysis
The Skill instructs the agent to retrieve a template and immediately install its dependencies. It does not require an immutable template version, trusted source validation, integrity hash, reviewed lockfile, dependency audit, or suppression of package lifecycle scripts.
An
npm installorpnpm installoperation may execute lifecycle scripts such aspreinstall,install, andpostinstall. Consequently, the downloaded template and its transitive dependency graph form a local code-execution channel. If the template source, lockfile, registry, or dependency is compromised, attacker-controlled code can run before the project is reviewed.Performing this installation automatically “during credential/Trust wait” increases exposure because the environment may contain active authentication material while reducing the opportunity for manual inspection. The history does not establish that the template or dependencies are malicious, so this is an insecure supply-chain workflow rather than confirmed intentional malware.
Attack Path
- An attacker compromises or influences the template distribution service, a mutable template release, its manifest ...[truncated 1299 chars]
- Remediation
View remediation
Remediation Suggestions
- Restrict
downloadTemplateto an explicitly approved registry or repository. - Pin templates to immutable versions, commit hashes, or content digests and verify integrity before use.
- Require a reviewed, committed lockfile and use frozen installation modes such as
npm ciorpnpm install --frozen-lockfile. - Disable lifecycle scripts by default with
--ignore-scripts; enable only individually reviewed scripts when required. - Audit direct and transitive dependencies for unexpected sources, install hooks, dependency confusion, and known vulnerabilities.
- Separate dependency installation from credential handling. Run installation in a sandbox with minimal environment variables, filesystem access, and network permissions.
- Present the template source, resolved version, integrity result, and planned install command for approval before execution.
- Avoid automatic background installation during the credential or trust workflow unless equivalent provenance verification and isolation controls are enforced.
- Restrict
