T08 · Insecure Dependencies
- Location
SKILL.md:196- Finding
Unpinned Global Installation of Third-Party Browser Automation Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 196–198
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumTechnical Analysis
The installation instructions globally install
agent-browserwithout specifying an exact version or verifying package integrity:bash npm install -g agent-browser agent-browser install # Download Chromium agent-browser install --with-deps # Linux: + system depsBecause no version or integrity hash is specified, the installed code depends on whichever package version the npm registry resolves at execution time. The effective package and downloaded browser artifacts can therefore change after this skill has been reviewed.
A global npm installation may also execute package lifecycle scripts with the privileges of the user running the command. The subsequent installation commands download additional browser and, in the
--with-depscase, system dependency artifacts without a documented version or integrity-verification policy.The reviewed files do not demonstrate that the current upstream package is malicious. The issue is the unsafe, mutable dependency installation process and its exposure to a future compromised release, registry compromise, maintainer-account takeover, or other supply-chain incident.
Attack Path
- An attacker compromises the upstream npm package, its publishing account, or another component of its distribution channel.
- The attacker publishes a malicious release under the same package name.
- A user or agent follows the documented
npm install -g agent-browserinstruction. - npm resolves the unpinned dependency to the attacker-controlled release.
- Malicious lifecycle or runtime code executes under the installing user's account.
- The globally installed executable may subsequently intercept browser automation inputs, session state, cookies, credentials, form contents, ...[truncated 614 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm package to a reviewed exact version, for example:
bash npm install -g agent-browser@<reviewed-exact-version> - Record and verify the expected npm package integrity digest before installation.
- Pin the Chromium/browser revision and verify downloaded artifact checksums or signatures.
- Prefer a project-local, lockfile-controlled installation over a global installation.
- Install and run the tool as an unprivileged, isolated user or inside a sandbox/container.
- Avoid
--with-depsunless system dependencies are necessary and their package sources and versions have been reviewed. - Disable npm lifecycle scripts during installation where compatible, then explicitly run only reviewed setup operations.
- Document the trusted publisher, package source, reviewed version, and update-review procedure.
- Pin the npm package to a reviewed exact version, for example:
