T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:20
- Finding
- Unpinned Third-Party Package Installation Creates Supply-Chain Risk## Vulnerability Details **File Location**: `SKILL.md`, lines 20-24 **Vulnerability Type**: Unpinned third-party dependency installation **Risk Level**: Medium **Vulnerable Code**: ```bash npm install orbcafe-ui # or pnpm add orbcafe-ui ``` ### Technical Analysis The installation instructions do not specify an exact reviewed version or package integrity value. Consequently, the package manager resolves the dependency to the registry version that satisfies its default resolution behavior at installation time. This makes the installed code mutable after the Skill has been reviewed. If the package publisher account, registry entry, or a future package release is compromised, users following these instructions could receive malicious code. npm and pnpm packages can define lifecycle scripts that execute during installation. Malicious package code could also execute later when the documented component is imported or used. ### Attack Path 1. An attacker compromises the `orbcafe-ui` package, its publisher account, or its release process. 2. The attacker publishes a malicious package version containing an installation lifecycle script or malicious runtime code. 3. A user follows the documented `npm install orbcafe-ui` or `pnpm add orbcafe-ui` instruction. 4. The package manager resolves and downloads the malicious mutable release. 5. Malicious lifecycle code executes during installation, or malicious runtime code executes when the package is imported by the application. ### Impact Assessment Exploitation could execute code with the privileges of the user or automation account running the package manager. Depending on the installation environment, this may expose source code, environment variables, package-registry credentials, deployment tokens, SSH material, or other files accessible to that account. In a CI/CD environment, compromise could affect build artifacts, downstream deployments, and other projects accessible w ...[truncated 205 chars]
- Remediation
- ## Remediation Suggestions - Pin `orbcafe-ui` to an exact version that has been reviewed instead of relying on mutable default resolution. - Commit the generated lockfile and require deterministic installation through `npm ci` or the pnpm equivalent with a frozen lockfile. - Verify package provenance, publisher identity, release history, integrity metadata, and lifecycle scripts before adoption. - Use dependency scanning and automated monitoring for package compromise and known vulnerabilities. - Consider initially installing with lifecycle scripts disabled, such as `npm install --ignore-scripts`, and explicitly review any scripts before allowing them. - Run dependency installation in an isolated, least-privileged build environment without unnecessary credentials or access to sensitive host files. - Document the reviewed package version and upgrade process so dependency changes receive a new security review.