Selenium Browser Control

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill mostly matches browser automation, but it includes undisclosed anti-detection behavior and weaker browser containment while exposing powerful actions like JavaScript execution and cookie access.

Install only if you intentionally want Selenium to drive a headless browser. Use it on trusted sites where automation is allowed, avoid sensitive logged-in sessions unless needed, be careful with cookie and JavaScript commands, and consider running it in an isolated environment because the script disables Chrome's sandbox and includes anti-detection settings.

Findings (5)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

A malicious or compromised site opened through the tool may have less browser isolation than the user expects.

Why it was flagged

The tool can open arbitrary URLs while launching Chrome with its sandbox disabled, which weakens containment for web content.

Skill content
options.add_argument("--no-sandbox") ... self.driver.get(url)
Recommendation

Avoid --no-sandbox unless running inside a separate isolated container; disclose the setting and prefer the normal Chrome sandbox for general browsing.

What this means

Users may unknowingly automate sites in a way that bypasses basic bot-detection expectations or violates site policies.

Why it was flagged

The implementation masks Selenium automation indicators, but SKILL.md only describes normal browser control and does not disclose this anti-detection behavior.

Skill content
options.add_argument("--disable-blink-features=AutomationControlled") ... # 反检测 ... Object.defineProperty(navigator, 'webdriver', {get: () => undefined})
Recommendation

Clearly disclose or remove anti-detection behavior, and use the skill only on sites where automation is permitted.

What this means

JavaScript run on a logged-in or sensitive page can read or change page data in that browser session.

Why it was flagged

The advertised JavaScript command is implemented by executing caller-supplied JavaScript inside the active page.

Skill content
def execute_script(self, script): ... result = self.driver.execute_script(script)
Recommendation

Only run JavaScript that the user explicitly requested and understands, especially on authenticated sites.

What this means

Cookie values could expose logged-in session state if used on authenticated websites.

Why it was flagged

The skill can return cookies from the automated browser session; this is documented functionality, but cookies can represent account sessions.

Skill content
cookies = self.driver.get_cookies(); return {"success": True, "cookies": cookies}
Recommendation

Avoid using the cookie commands on sensitive accounts unless necessary, and do not share tool outputs containing cookies.

What this means

Installation depends on whatever package and driver versions the user obtains, which can affect reliability and trust.

Why it was flagged

The setup relies on an unpinned PyPI package and external ChromeDriver while the registry has no install spec or declared required binaries.

Skill content
pip install selenium ... 需要 Chrome 浏览器和 ChromeDriver。
Recommendation

Install Selenium and ChromeDriver from trusted sources, pin versions where possible, and verify ChromeDriver matches the installed browser.