T09 · Insecure Skill Coding Practices
- Location
index.mjs:108- Finding
Full-page screenshots and API credentials can be transmitted to an unrestricted endpoint
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a real captcha automation tool, but it needs Review because it uploads full-page screenshots to a configurable vision API and can fill and submit arbitrary webpage forms without confirmation.
Install only if you are comfortable with full-page webpage screenshots and your vision API key being sent to the configured model endpoint. Use it only on non-sensitive, trusted captcha pages, prefer a dedicated low-privilege API key and isolated workspace/browser profile, avoid pages with passwords or personal/account data, and be aware it may click submit or login-style buttons automatically.
index.mjs:108Full-page screenshots and API credentials can be transmitted to an unrestricted endpoint
index.mjs:393Unvalidated output prefix permits screenshot writes outside the workspace
index.mjs:346Weak heuristics can fill and submit an unrelated webpage form
index.mjs:591Chromium is launched with its process sandbox disabled
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
ls -la ~/.openclaw/workspace/skills/captcha-auto/
rm -rf ~/skills/captcha-auto cd ~/.openclaw/workspace clawhub install captcha-auto
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
ls -la ~/.openclaw/workspace/skills/captcha-auto/
rm -rf ~/skills/captcha-auto cd ~/.openclaw/workspace clawhub install captcha-auto
Referenced artifact was not completely inspected
node scripts/run.mjs --url="https://example.com" --api-key="sk-xxx" --model="qwen3-vl-plus"
Referenced artifact was not completely inspected
node scripts/run.mjs --url="https://example.com" --api-key="sk-xxx" --model="qwen3-vl-plus"
Referenced artifact was not completely inspected
node scripts/run.mjs --url="https://example.com" --api-key="sk-xxx" --model="qwen3-vl-plus"
Referenced artifact was not completely inspected
node scripts/run.mjs --url="https://example.com" --api-key="sk-xxx" --model="qwen3-vl-plus"
Referenced artifact was not completely inspected
node scripts/run.mjs --url="https://example.com" --api-key="sk-xxx" --model="qwen3-vl-plus"
Referenced artifact was not completely inspected
node scripts/run.mjs --url="https://example.com" --api-key="sk-xxx" --model="qwen3-vl-plus"
The skill explicitly requires environment variables and outbound network access to a third-party API, but its manifest does not declare any tool scope or permissions. This creates a transparency and least-privilege problem: an agent or user cannot accurately assess what the skill will access before installation or execution.
This markdown file presents the skill description and operating instructions exclusively in Chinese, which effectively forces a specific language on users. The policy allows locale constraints only when users are given a choice or when the constraint is clearly justified as region-specific, neither of which is stated here.
Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.
# 正确位置
ls -la ~/.openclaw/workspace/skills/captcha-auto/
# 如果装错了(在 ~/skills/),删除并重新安装
rm -rf ~/skills/captcha-auto
Code scans file system directories looking for sensitive files. This could be reconnaissance for credential theft.
# 正确位置
ls -la ~/.openclaw/workspace/skills/captcha-auto/
# 如果装错了(在 ~/skills/),删除并重新安装
rm -rf ~/skills/captcha-auto
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Linux:安装 Chromium
sudo apt install chromium-browser
The skill sends a full-page screenshot to an external vision API even though its stated purpose is only captcha recognition. This can exfiltrate unrelated page contents such as personal data, session-bound content, or sensitive UI state to a third party, and the risk is amplified because the code explicitly automates browsing arbitrary URLs.
After guessing an input field, the skill also guesses and clicks submit/verify/login buttons automatically. This expands the capability from passive captcha assistance into active page interaction, which can trigger unintended account actions, form submissions, authentication attempts, or workflow changes on arbitrary sites without explicit confirmation.
The skill performs potentially state-changing clicks on likely submit or verify controls without any user confirmation step. In the context of arbitrary web automation, heuristic clicking can cause unauthorized or unintended actions, especially when selectors also match login or confirmation buttons.
The help text claims a local-OCR-first hybrid privacy-preserving flow, but the implementation always skips local OCR for the full-page flow and proceeds to the external vision model. This mismatch can mislead users about where their data goes, undermining informed consent and causing unexpected third-party disclosure of page content.
This code presents user-facing instructions, help text, and status messages exclusively in Chinese. That creates a language/locale restriction without any opt-in, fallback, or justification that the skill is intended only for a Chinese-speaking audience.
The file's user-facing help, logs, errors, and instructions are consistently presented in Chinese, with no indication that the user can choose another language. This is a natural-language policy concern when a skill imposes a locale without opt-in or a documented region-specific justification.
A captcha recognition skill would reasonably need model credentials, but this implementation pulls them from broad ambient sources including process environment variables and a user-wide OpenClaw config file. That capability is not part of the stated functional purpose and increases access to unrelated local secrets/configuration.
The natural-language description is written entirely in Chinese and does not indicate that users can choose another language or that the skill is intentionally limited to a Chinese-speaking context. Under the policy, locale or language constraints should be optional or clearly justified rather than implicitly imposed.
Using a caret range for playwright-core allows installation of newer minor/patch releases that have not been explicitly reviewed, which weakens build reproducibility and increases supply-chain risk. In an automation skill that drives a browser, dependency drift could introduce vulnerable or malicious code paths affecting browser control, network access, or local execution context.
"author": "Lie Troksky and Aphrodite",
"license": "MIT",
"dependencies": {
"playwright-core": "^1.40.0",
"tesseract.js": "^5.0.0"
},
"scripts": {
Using a non-pinned version for tesseract.js permits unreviewed dependency updates and reduces reproducibility, creating a supply-chain exposure. This skill processes CAPTCHA images and OCR content, so changes in the dependency tree could affect how untrusted image data is handled and may introduce vulnerable transitive packages.
"license": "MIT",
"dependencies": {
"playwright-core": "^1.40.0",
"tesseract.js": "^5.0.0"
},
"scripts": {
"test": "node index.mjs",
The manifest references tesseract.js without pinning an exact version, while the package has a known advisory for insecure default configuration. Because the installed release is not fixed or constrained here, consumers may resolve to an affected version, which is especially relevant in a skill that accepts and OCR-processes externally sourced CAPTCHA images.
Detected: suspicious.env_credential_access, suspicious.exposed_secret_literal