T08 · Insecure Dependencies
- Location
scripts/run_agent_browser_on_tabbit.py:58- Finding
Unpinned Third-Party Package Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
scripts/run_agent_browser_on_tabbit.py, lines 58–59
Vulnerability Type: Unpinned dependency execution throughnpx
Risk Level: Mediumpython if shutil.which("npx"): return ["npx", "--yes", "agent-browser"]Technical Analysis
When a locally installed
agent-browserexecutable is unavailable, the wrapper automatically falls back tonpx --yes agent-browser. This command may retrieve and execute the package currently published under that name without an exact version, lockfile, integrity constraint, or interactive approval.Consequently, the effective code executed by the audited skill can change after review. The trust boundary extends to the package registry, the package publisher, and the package's transitive dependency chain. The
--yesoption removes the normal opportunity for the user to review or reject package installation.Attack Path
- The victim invokes
scripts/run_agent_browser_on_tabbit.py. - No
agent-browserexecutable is available onPATH, butnpxis installed. - The wrapper selects
npx --yes agent-browserautomatically. npxresolves the unpinned package through its configured registry and may download it and its dependencies.- A compromised or malicious package release executes with the privileges of the user running the wrapper.
- The package receives the Tabbit CDP WebSocket endpoint and browser-operation arguments, enabling it to interact with the connected browser session.
Exploitation depends on compromise or malicious control of the resolved package, its publisher, the configured registry, or its dependency chain.
Impact Assessment
Malicious package code could execute arbitrary commands with the invoking user's operating-system privileges and access files, environment variables, and network resources available to that user. Because the wrapper supplies a live Chrome DevTools Protocol endpoint, the malicious code could also control Ta ...[truncated 330 chars]
- The victim invokes
- Remediation
View remediation
Remediation Suggestions
- Remove the automatic
npx --yesfallback and require a preinstalled, explicitly trustedagent-browserexecutable by default. - If
npxsupport is required, pin an audited exact package version, for exampleagent-browser@<exact-version>, rather than resolving the latest release. - Use a lockfile and registry-supported integrity verification to pin both the direct package and its transitive dependencies.
- Require explicit user confirmation before any package is downloaded or executed; do not use
--yesfor an implicit fallback. - Restrict package resolution to an approved registry and document the expected package publisher and version.
- Prefer installation during a controlled setup phase instead of downloading executable code during browser automation.
- Verify the resolved executable or package artifact against an approved checksum or signature before launching it.
- Fail closed with a clear installation message when no trusted binary is available.
- Remove the automatic
