T08 · Insecure Dependencies
- Location
references/agent-friendly-pages.md:126- Finding
Unpinned Package Download and Execution via npx
- Content
View full analysis
Vulnerability Details
File Location:
references/agent-friendly-pages.md:126
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable code:
bash CLI `npx lighthouse@latest <url> --only-categories=agentic-browsing` (per-auditTechnical Analysis
The documented command directs
npxto resolve and execute Lighthouse using the mutablelatestdistribution tag. If the package is not already available locally,npxmay retrieve executable package content from the configured npm registry.Because neither an exact version nor an integrity-protected lockfile is specified, the effective code can change after the Skill has been reviewed. A compromised npm publisher account, malicious package release, registry compromise, or compromised transitive dependency could therefore introduce arbitrary code into the command's execution path.
This is classified as
T08: Insecure Dependenciesbecause the primary weakness is unsafe, unpinned dependency acquisition. The reviewed instruction does not itself identify a malicious package or deliberately retrieve a known malicious payload.Attack Path
- An attacker compromises the Lighthouse publishing account, package supply chain, registry resolution path, or a dependency included by a future release.
- The attacker publishes malicious code in a release selected by the
latesttag. - A user or agent follows the Skill's documented command.
npxresolves the mutable tag and downloads the affected package when it is not safely available locally.- The package executes under the invoking process's operating-system identity.
- The malicious code can access resources available to that identity and perform further local or network operations.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user or agent running
npx. The potential scope includes rea ...[truncated 309 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
lighthouse@latestwith an exact, reviewed version, for examplelighthouse@13.4.0, after independently verifying that version. - Install dependencies in a separate controlled step using a committed lockfile and integrity verification.
- Prefer a preinstalled, trusted Lighthouse binary in automated environments.
- Use
npx --no-install lighthouse ...after controlled installation to prevent implicit network retrieval during the audit. - Apply dependency scanning and periodically review pinned upgrades before changing the approved version.
- Run the audit tool in a restricted environment with minimal filesystem access, no unnecessary credentials, and constrained outbound networking.
- Replace
