T08 · Insecure Dependencies
- Location
SKILL.md:30- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 30-36; repeated at lines 49, 65, and 77-81
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: HighVulnerable Code
bash # Single service npx osv-ui --no-open --json ./osv-report.json # Multiple services npx osv-ui ./frontend ./api ./worker --no-open --json ./osv-report.json # Auto-discover npx osv-ui --discover --no-open --json ./osv-report.jsonAdditional unpinned invocations include:
bash npx osv-ui [same paths] npx osv-ui --no-open --json ./osv-report-after.json npx osv-ui npx osv-ui ./frontend ./api npx osv-ui --discover npx osv-ui --json=report.json --no-open npx osv-ui --html=report.html --no-openTechnical Analysis
The Skill instructs the Agent to execute
osv-uithroughnpxwithout specifying an exact package version or verifying package integrity. If the package is not already available locally,npxcan retrieve and execute the current package release from the configured npm registry.Consequently, the code executed during an audit is mutable and may differ from the code reviewed when this Skill was published. The project contains no vendored implementation, package lockfile, integrity hash, or other mechanism that binds execution to a specific audited artifact. The confirmation requirement in the Skill applies only to dependency fixes and does not protect the initial
npxexecution.This creates a supply-chain execution boundary: compromise of the upstream package, npm publisher account, registry resolution, or local registry configuration could cause attacker-controlled JavaScript to execute with the permissions of the Agent or user.
Attack Path
- An attacker compromises the upstream
osv-uipackage, its publisher account, or a registry/mirror used by the environment. - The attacker publishes or serves a malicious package release under the expected package ...[truncated 1349 chars]
- An attacker compromises the upstream
- Remediation
View remediation
Remediation Suggestions
-
Pin
osv-uito a reviewed, exact version in every command rather than resolving the latest release:bash npx --yes osv-ui@1.0.0 --no-open --json ./osv-report.json -
Install the pinned dependency through a committed lockfile and use a deterministic installation method such as
npm ci. Review and preserve the registry-provided integrity value in the lockfile. -
Verify the package's publisher, provenance, release signatures where available, repository correspondence, and npm integrity metadata before trusting it.
-
Require explicit user confirmation before downloading or executing the package, rather than requiring confirmation only before applying dependency upgrades.
-
Run the scanner in a restricted environment with:
- Read-only access to the project where practical.
- No access to unrelated home-directory files or credential stores.
- Minimal environment variables.
- Restricted outbound network access.
- No elevated operating-system privileges.
-
Avoid globally configured or untrusted npm registries and mirrors. Explicitly use a trusted registry and enforce dependency allowlisting where supported.
-
Update every repeated invocation in
SKILL.md, including the dashboard, verification, and quick-reference commands, so none can silently fall back to an unpinned package release.
-
