T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:76- Finding
Mutable Remote Executable Is Downloaded and Run Without Integrity Verification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a powerful desktop-control skill with disclosed purpose, but its unverified executable install path, broad remote API trust, screenshot/file upload behavior, and plaintext token handling need review before use.
Install only if you trust the ScreenClaw service and its GitHub release source. Prefer a pinned, verified binary, rotate away from the documented default token, keep the API bound to localhost or HTTPS trusted origins, avoid remote servers unless necessary, and do not use delegated mode or desktop automation on passwords, payments, security prompts, destructive dialogs, or confidential screens without explicit review.
SKILL.md:76Mutable Remote Executable Is Downloaded and Run Without Integrity Verification
scripts/_common.py:246Arbitrary Local Files Can Be Encoded and Uploaded to a Configurable Remote Server
scripts/screenclaw.py:69Bearer Tokens and Desktop-Automation Data May Be Sent Over Plaintext or to Arbitrary Origins
references/self_check.md:129Remote API Responses Can Trigger Agent Workflow Changes and Transmission of Task Context
references/config.md:18Published Default Authentication Token Creates Predictable Credentials
scripts/screenclaw.py:6Runtime Dependency Installation Is Unpinned and Lacks Integrity Verification
声明描述的是一个完整的 Windows 桌面 RPA/视觉自动化技能,核心能力应包括截图、识别屏幕元素坐标、执行鼠标键盘操作,以及录制并复用场景模板。实际代码则是一个分析脚本:从 step.json 中读取已录制的步骤,按窗口/弹窗/子窗口等类型分组,生成摘要表和警告。它最多可视为“录制后处理/模板整理”的辅助组件,但无法单独支撑声明的主要用途。由于代码的主要行为与描述的核心自动化能力明显不符,应判定为描述与行为不匹配。
The skill is capable of broad desktop interaction—clicks, typing, dragging, handling file pickers, and controlling arbitrary third-party applications—yet the description does not present a clear safety warning or consent boundary. In context, this is especially dangerous because the skill explicitly targets software that normal APIs cannot cover, including strict anti-abuse environments, hidden UI, games, and system-level surfaces, which raises the risk of unintended destructive actions or misuse against sensitive interfaces.
The skill describes capabilities that require broad file, environment, and network access but does not declare any explicit tool scope or permission boundaries. For a desktop-automation skill, this is dangerous because it can lead to over-privileged execution, including reading local files, modifying config/templates, downloading binaries, and contacting external services without a clear allowlist or user-visible constraint.
The activation guidance is extremely broad, effectively routing many generic requests about clicking, inputting, automation, games, desktop software, and cross-window actions into a powerful desktop-control skill. Over-broad triggers increase the chance of accidental invocation in sensitive contexts, causing the agent to manipulate third-party apps or system UI when a lower-risk skill or simple textual assistance would have been more appropriate.
The documentation exposes powerful batch desktop/window automation primitives—clicking, typing, key presses, drag/drop, and scrolling—without any guardrails, warning language, confirmation requirements, or scope restrictions. In the context of this skill, which is explicitly designed to operate arbitrary Windows applications and cross-window flows, these actions can be combined to perform destructive or sensitive operations such as sending messages, changing settings, moving files, confirming dialogs, or interacting with security-sensitive UIs at machine speed.
The documentation explicitly states that in remote scenarios the local screenshot file is converted to base64 and sent to a server, but it does not warn users that screenshots may contain sensitive on-screen data such as credentials, chats, personal information, or proprietary application content. In this skill’s context, screenshots are taken from arbitrary desktop software and security-sensitive webpages, which materially increases the privacy and data-exfiltration risk if users are unaware of the transmission boundary.
The file explicitly states that when delegated mode is active, click confirmation is automatically skipped. In a skill designed to control arbitrary desktop software via screenshot-derived coordinates, removing confirmation increases the chance of unintended or unsafe UI actions, including clicks on sensitive controls, security prompts, or destructive buttons if the model misreads the screen or the UI changes.
The documentation explicitly states that in hijack mode, confirmation is automatically skipped for a desktop double-click action. In a skill designed to control arbitrary desktop software via screenshots and coordinates, bypassing confirmation increases the chance of unintended or unauthorized UI actions, especially against sensitive applications, dialogs, or security prompts.
The documentation explicitly describes a desktop drag capability in fixed hijack mode and notes that delegated mode can skip confirmation, yet it lacks a clear safety warning about direct UI manipulation. In this skill's context—general-purpose automation of arbitrary desktop software, including security-sensitive apps—drag actions can move files, rearrange UI state, trigger destructive operations, or interact across windows and monitors without meaningful user awareness.
The natural-language content of this markdown file is entirely in Chinese, including the description, headings, and parameter explanations, with no indication that the skill supports other languages or that Chinese-only use is required for a region-specific purpose. This creates a locale/language policy concern because the skill effectively imposes a language constraint without user opt-in or documented justification.
The documentation explicitly states that the tool will click to steal focus and then paste via the clipboard in a fixed hijack mode, with confirmation skipped in delegated mode. In a desktop automation skill intended to operate arbitrary Windows applications, this can overwrite the user's clipboard, send sensitive text to the wrong window, and trigger unintended actions in privileged or security-sensitive contexts without an adequate warning or consent boundary.
The documentation states the action runs in fixed hijack mode and that confirmation is automatically skipped when delegated mode is active, while also supporting system-level shortcuts such as Win and Alt+Tab. In the context of a desktop automation skill that can control arbitrary Windows software, this removes an important user-consent barrier and enables unintended or unsafe system-wide input injection, including focus switching, launching menus, or affecting privileged windows.
The documentation states that in delegated mode confirmation is automatically skipped for a desktop right-click action. In a skill explicitly designed to control arbitrary Windows software through screen coordinates, bypassing confirmation increases the chance of unintended or unauthorized UI interaction, especially because right-click context menus can expose destructive actions such as delete, run-as-admin, or security-sensitive workflow steps.
The API documentation explicitly enables full-desktop screenshot capture and transmission/return of image data, but it does not warn that the capture may include sensitive information from unrelated applications, notifications, credentials, personal data, or other monitors' visible content. In this skill's context, desktop-wide visual automation is a core capability and is intended for arbitrary software, which materially increases the risk of over-collection, privacy leakage, and accidental exfiltration to remote services or models.
The natural-language content of the skill file is entirely in Chinese, including the description and usage guidance, with no indication that language is selectable or that the skill is region-specific. Under the policy rule, forcing a specific language without user opt-in can be a locale policy violation.
The documentation explicitly states that in delegated mode confirmation is automatically skipped for a desktop-input action. In the context of a skill designed to control arbitrary Windows applications via mouse and keyboard, this removes an important safety barrier and increases the risk of unintended or unauthorized input on the user's system.
The file’s user-facing instructions are entirely in Chinese, with no indication that language selection is optional or that the skill is specifically limited to a Chinese-speaking context. Under the policy, forcing a specific language without user opt-in is a natural-language policy violation.
The file’s natural-language content, including the description, usage guidance, and troubleshooting, is entirely in Chinese. This imposes a specific language on users without any documented opt-in or indication that the skill is intentionally region-specific, which matches the language/locale policy violation criteria.
This file’s natural-language content, including the description and usage guidance, is entirely in Chinese. Under the policy rule, forcing a specific language without user opt-in or a documented justification is a locale/language policy concern.
The file’s user-facing description and instructions are entirely in Chinese, which imposes a specific language on users. Under the policy, language constraints should either be optional for the user or explicitly documented as a justified locale-specific limitation.
文件标题和说明均以中文固定呈现,未表明这是可选语言,也未提供其他语言或用户选择机制。根据 SQP-3,若技能在自然语言层面强制特定语言/locale 且无用户 opt-in,可构成语言/地区策略违规。
The documentation states that the API returns a local image path and may materialize base64 screenshot data to disk, but it does not warn that scrolling screenshots can capture sensitive on-screen content such as chats, documents, credentials, or regulated data across multiple viewport segments. In this skill’s context—desktop automation of arbitrary apps, including chat tools and high-friction websites—the omission increases the risk of unintended bulk data collection and local persistence without informed user awareness.
The document says not to guess or use defaults, yet it publishes a concrete default localhost endpoint and bearer token. In practice, an agent or user may still use these values, enabling unauthorized control of a locally running ScreenClaw service if that service ships with the same static token or if the token is widely reused. Given this skill can drive arbitrary desktop input, compromise of the local agent-to-service channel can translate into full desktop automation abuse.
The configuration instructs saving and reusing user-provided authentication details directly in the skill file, which creates a plaintext secret persistence channel inside agent assets. Anyone with access to the skill files, logs, backups, or version control could recover the token and invoke the desktop automation service, potentially performing arbitrary clicks, keystrokes, and data entry on the user's machine.
The manifest-style description is written as a Chinese-only requirement/description and provides no indication that users may choose another language or locale. Under the policy, forcing a specific language without opt-in is a natural-language locale violation.
No suspicious patterns detected.