T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned Globally Installed Third-Party Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 17–20
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumCode Snippet:
bash ### Step 1: Install agent-browser ```bash npm install -g agent-browsertext The installation instruction is also repeated at `SKILL.md:633`: ```markdown - **agent-browser**: `npm install -g agent-browser`Technical Analysis
The Skill instructs users to install the latest available version of the
agent-browsernpm package globally without pinning a reviewed version, verifying package integrity, or identifying an authoritative repository. As a result, the code installed and executed can change after the Skill has been audited.A global npm installation may execute package lifecycle scripts with the privileges of the user running npm. It also places package-provided executables in a global command path. If the package, a transitive dependency, the maintainer account, or the package-distribution channel is compromised, following this instruction could install and execute unauthorized code.
The audit did not establish that the named package is currently malicious. The vulnerability is the unsafe and non-reproducible dependency installation process.
Attack Path
- An attacker compromises the npm package, one of its dependencies, or a maintainer publishing account.
- The attacker publishes a malicious release or introduces a malicious lifecycle script.
- A user follows the Skill instruction and runs
npm install -g agent-browser. - npm retrieves the latest release rather than a previously audited version.
- Malicious lifecycle code can execute during installation, or a malicious globally installed CLI can execute when later invoked.
- The payload operates with the installing user's privileges and can access resources available to that account.
Impact Assessment
Successful exploitation could result in arbitrary c ...[truncated 637 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a specific, reviewed version rather than installing the latest release:
bash npm install --save-exact agent-browser@<reviewed-version> - Prefer a project-local installation with a committed lockfile over a global installation.
- Document the package's authoritative npm scope and official source repository so users can detect similarly named or spoofed packages.
- Verify package provenance and integrity before installation, including published checksums or npm provenance attestations where available.
- Audit both the direct package and its transitive dependencies before approving version updates.
- Consider disabling lifecycle scripts during installation when compatible:
bash npm install --ignore-scripts --save-exact agent-browser@<reviewed-version> - Apply dependency updates through a controlled review process rather than resolving an unrestricted version at installation time.
- Avoid running npm with
sudo, an administrator account, or other elevated privileges.
- Pin the dependency to a specific, reviewed version rather than installing the latest release: