Back to skill

Security audit

Super Agent Browser

Security checks for vulnerabilities and agentic risk

Overview

This browser automation skill is mostly coherent, but it needs Review because it encourages saving and reusing authenticated browser state and uses an unpinned global install without enough security guidance.

Before installing, pin and verify the `agent-browser` package where possible, avoid running install commands with elevated privileges, and treat saved browser state files as secrets. Do not commit auth JSON files, do not load state files from untrusted sources, isolate sessions by account or task, and redact cookies, storage values, credentials, and authenticated page content from logs or shared outputs.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
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: Medium

Technical Analysis

The installation instructions globally install agent-browser without 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 deps

Because 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-deps case, 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

  1. An attacker compromises the upstream npm package, its publishing account, or another component of its distribution channel.
  2. The attacker publishes a malicious release under the same package name.
  3. A user or agent follows the documented npm install -g agent-browser instruction.
  4. npm resolves the unpinned dependency to the attacker-controlled release.
  5. Malicious lifecycle or runtime code executes under the installing user's account.
  6. The globally installed executable may subsequently intercept browser automation inputs, session state, cookies, credentials, form contents, ...[truncated 614 chars]
Remediation
View remediation

Remediation Suggestions

  1. Pin the npm package to a reviewed exact version, for example:
    bash
    npm install -g agent-browser@<reviewed-exact-version>
    
  2. Record and verify the expected npm package integrity digest before installation.
  3. Pin the Chromium/browser revision and verify downloaded artifact checksums or signatures.
  4. Prefer a project-local, lockfile-controlled installation over a global installation.
  5. Install and run the tool as an unprivileged, isolated user or inside a sandbox/container.
  6. Avoid --with-deps unless system dependencies are necessary and their package sources and versions have been reviewed.
  7. Disable npm lifecycle scripts during installation where compatible, then explicitly run only reviewed setup operations.
  8. Document the trusted publisher, package source, reviewed version, and update-review procedure.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

This skill explicitly supports saving/loading browser auth state, inspecting cookies/storage, and running isolated sessions, but it provides no warnings about the sensitivity of cookies, localStorage, saved auth files, or data extracted from authenticated sites. In an agent context, that omission is dangerous because it increases the likelihood that users or downstream agents will persist, expose, or reuse session material insecurely, enabling account takeover, cross-session data leakage, or unintended disclosure of sensitive site data.

Content

No source excerpt is available for this finding.