chrome-relay-browser
Security checks across malware telemetry and agentic risk
Overview
This skill transparently controls a user-attached Chrome tab through a local relay, but it gives the agent powerful live-browser abilities that should be used only on intended pages.
Install only if you want OpenClaw to control visible Chrome tabs you manually attach. Keep the relay token private, attach only the intended tab, and supervise actions on logged-in or sensitive websites.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
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.
An agent using this skill can read or change the currently attached web page and may act within already logged-in browser sessions.
The tool intentionally allows arbitrary JavaScript evaluation in the attached Chrome tab, alongside navigation, screenshot, click, and fill operations.
case 'evaluate': { const js = args.join(' '); const result = await sendCommand(ws, 'Runtime.evaluate', { expression: js });Attach only the tab you intend the agent to control, avoid sensitive accounts unless needed, and require explicit confirmation before submitting forms, purchases, account changes, or other irreversible actions.
Anyone or any process with access to the relay token and local relay could potentially control attached Chrome tabs.
The skill uses a local relay token that grants access to the browser relay; this is disclosed and expected, but it is still a sensitive credential.
Token 和 Port 存储在 `~/.openclaw/secrets/browser-relay.env`，脚本自动读取：- `RELAY_TOKEN` - Gateway token
Protect the secrets file, rotate the relay token if exposed, and detach tabs or disable the relay when browser automation is not needed.
The skill may fail unless the dependency is already available, or it may rely on an ambient package outside the reviewed artifacts.
The script depends on the external 'ws' Node module, but the provided install specification says there is no install spec, so dependency provenance and setup are not fully described.
const WebSocket = require('ws');Use a pinned package/install specification or document the trusted source of the WebSocket dependency.