T08 · Insecure Dependencies
- Location
references/SKILL.md:197- Finding
Unpinned Global Third-Party Package Installation
- Content
View full analysis
Vulnerability Details
File Location:
references/SKILL.md, lines 197-201
Vulnerability Type: Unpinned dependency installation and supply-chain exposure
Risk Level: MediumVulnerable Code:
bash ## Installation ```bash npm install -g agent-browser agent-browser install # Download Chromium agent-browser install --with-deps # Linux: + system depsTechnical Analysis
The documentation instructs users to install
agent-browserglobally without specifying an exact package version or integrity value. The reviewed skill therefore does not determine which package implementation will be installed. A later release, compromised publisher account, registry compromise, or malicious dependency update could introduce code that was not present during this audit.npm installation can execute package lifecycle scripts with the installing user's privileges. The subsequent
agent-browser installcommand downloads additional browser components, whileagent-browser install --with-depsmay install or modify operating-system dependencies. These operations increase the trusted supply-chain surface beyond the static files included in this project.This finding does not establish that the current
agent-browserpackage is malicious. The vulnerability is the unsafe, unpinned installation procedure and the resulting inability to reproduce the reviewed dependency set.Attack Path
- An attacker compromises the package publisher, package registry, upstream release process, or a transitive dependency.
- The attacker publishes a modified version under the expected package name.
- A user follows the skill instructions and runs
npm install -g agent-browser. - npm retrieves the currently published version rather than a version reviewed and pinned by the project.
- Malicious lifecycle code or installed CLI code executes with the privileges of the installing user.
- If the use ...[truncated 866 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
agent-browserto an exact, audited version rather than installing the latest available release. - Verify and document the expected package publisher, upstream repository, release signature, and package integrity hash.
- Prefer a project-local dependency managed through a committed lockfile over a global installation.
- Disable or separately review npm lifecycle scripts where operationally possible.
- Run installation as an unprivileged user in an isolated environment or container.
- Document every system modification performed by
install --with-deps, and avoid that option unless the dependency list and installation script have been reviewed. - Pin and verify downloaded Chromium artifacts and transitive dependencies where the tool supports doing so.
- Periodically re-audit the pinned package before upgrading it.
- Pin
