T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unpinned Third-Party Installer Executes Mutable Supply-Chain Code
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 18–24
Vulnerability Type: Unpinned third-party dependency installation and execution
Risk Level: MediumVulnerable Code
markdown This skill drives the `olx-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer: ```bash npx -y @mvanhorn/printing-press install olx --cli-only- Verify:
olx-pp-cli --version
text ### Technical Analysis The installation command invokes `npx` with automatic confirmation and does not specify an exact package version or integrity digest. Consequently, the code executed depends on whichever release of `@mvanhorn/printing-press` the npm registry resolves at installation time. The installer then retrieves or installs the separate `olx-pp-cli` executable, whose version and checksum are likewise unspecified. This creates a mutable supply-chain trust path: reviewing the Skill does not establish which installer code or CLI binary will execute later. Compromise of the package publisher, npm artifact, transitive dependency, installer-controlled release source, or distribution process could turn the documented setup procedure into arbitrary code execution. Package lifecycle scripts may also execute during `npx` package preparation. The issue is classified as insecure dependency handling rather than confirmed embedded malware. The repository contains only `SKILL.md`; it does not contain the installer or CLI implementation, so no malicious behavior in those external components can be established from the audited artifact. ### Attack Path 1. An attacker compromises the npm publisher account, package release process, a relevant dependency, or an installer-controlled binary source. 2. The attacker publishes or serves a malicious artifact under the expected package or CLI identity. 3. An Agent loads this Skill on a system where ...[truncated 1138 chars]- Verify:
- Remediation
View remediation
Remediation Suggestions
- Pin
@mvanhorn/printing-pressto an exact reviewed version rather than relying on registry resolution:bash npx -y @mvanhorn/printing-press@X.Y.Z install olx --cli-only - Pin the exact
olx-pp-clirelease installed by the Printing Press tool. - Publish official SHA-256 checksums or signed provenance for installer and CLI artifacts, and verify them before execution.
- Prefer a documented official release source with signature verification over a dynamically resolved installer chain.
- Use a lockfile and integrity metadata where npm-based installation is unavoidable.
- Disable or strictly review package lifecycle scripts where operationally possible.
- Run installation in a sandbox or least-privileged environment without unrelated credentials or sensitive filesystem access.
- Document the trusted publisher, release URL, expected package scope, supported version, signature identity, and verification procedure.
- Verify more than command availability:
olx-pp-cli --versionshould be checked against an explicit approved version and the binary against a published digest or signature.
- Pin
