chrome-devtools

Fail

Audited by Gen Agent Trust Hub on Feb 17, 2026

Risk Level: HIGHCOMMAND_EXECUTIONEXTERNAL_DOWNLOADSDATA_EXFILTRATIONCREDENTIALS_UNSAFE
Full Analysis
  • [COMMAND_EXECUTION] (HIGH): The script scripts/evaluate.js uses eval() to execute arbitrary JavaScript strings provided as command-line arguments within the browser context. This allows for complete control over the browser session and page data.
  • [COMMAND_EXECUTION] (HIGH): In scripts/lib/browser.js, the browser is launched with the --no-sandbox and --disable-setuid-sandbox arguments. This disables the Chromium sandbox, meaning a malicious website could potentially escape the browser and execute code on the host machine.
  • [CREDENTIALS_UNSAFE] (MEDIUM): The scripts/lib/browser.js utility implements session persistence by saving the browser's WebSocket endpoint (wsEndpoint) to a local file named .browser-session.json. If this file is readable by other users or processes, they can connect to and take control of the active browser instance.
  • [PRIVILEGE_ESCALATION] (MEDIUM): The scripts/install-deps.sh script uses sudo to install numerous system libraries. While common for Puppeteer setup, users should verify the packages being installed.
  • [DATA_EXFILTRATION] (MEDIUM): The toolset provides broad capabilities to read cookies, headers, local storage, and network traffic (network.js, console.js, evaluate.js). If used on authenticated sessions (e.g., mail, internal tools), this data can be easily exfiltrated.
  • [EXTERNAL_DOWNLOADS] (LOW): The install.sh and install-deps.sh scripts perform several external downloads, including Chromium (via npm/puppeteer) and various Linux system libraries from official repositories.
Recommendations
  • AI detected serious security threats
Audit Metadata
Risk Level
HIGH
Analyzed
Feb 17, 2026, 06:18 PM