T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Third-Party Installation and Build Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 17–27
Vulnerability Type: Unpinned and mutable third-party dependencies
Risk Level: MediumVulnerable Code
bash npm install -g agent-browser agent-browser install agent-browser install --with-depsbash git clone https://github.com/vercel-labs/agent-browser cd agent-browser pnpm install pnpm build agent-browser installTechnical Analysis
Both installation methods retrieve mutable upstream content without pinning a reviewed npm package version, repository commit, dependency graph, or artifact checksum. The npm command resolves the version selected by the registry at installation time. The source installation clones the current default branch and then executes package installation and build processes.
npm and pnpm installation can execute package lifecycle scripts. Therefore, a compromised upstream release, repository, maintainer account, or transitive dependency could cause attacker-controlled code to run on the user's system. The
--with-depsoption can increase exposure by installing additional browser or system dependencies.The referenced package and repository are consistent with the Skill's stated browser-automation purpose. There is no evidence in the reviewed package that either upstream source is currently malicious; the risk arises from the mutable, unverified supply chain.
Attack Path
- An attacker compromises an upstream maintainer account, package release, repository, or transitive dependency.
- The attacker publishes malicious content under the otherwise legitimate dependency identity.
- A user follows the unpinned installation instructions in
SKILL.md. - npm or pnpm downloads the attacker-controlled version or dependency.
- Malicious lifecycle, dependency, or build code executes with the installing user's privileges.
- A compromised browser CLI may subsequently access data available d ...[truncated 731 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm dependency to a specific reviewed version rather than allowing registry-time resolution:
bash npm install -g agent-browser@<reviewed-version> - Pin source installations to an exact reviewed commit or signed release tag:
bash git clone https://github.com/vercel-labs/agent-browser cd agent-browser git checkout <reviewed-commit-sha> - Publish trusted SHA-256 checksums or signature-verification instructions for release artifacts.
- Use and enforce a lockfile for source builds, including frozen-lockfile installation.
- Avoid elevated installation privileges wherever possible and document the privilege implications of
agent-browser install --with-deps. - Review package lifecycle scripts and the resolved transitive dependency graph before recommending each new version.
- Establish a controlled update process that reviews and tests new upstream releases before changing the pinned version.
- Pin the npm dependency to a specific reviewed version rather than allowing registry-time resolution:
