Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

2Captcha CLI

v1.0.0

Solve CAPTCHAs using 2Captcha service via CLI. Use for bypassing captchas during web automation, account creation, or form submission.

0· 4.2k·18 current·18 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The SKILL.md and README consistently describe a CLI client for the 2Captcha service (image, reCAPTCHA, hCaptcha, Turnstile, etc.), which matches the skill name/description. However the registry metadata declares no required credentials or config paths, while the instructions clearly require a 2Captcha API key (TWOCAPTCHA_API_KEY or ~/.config/2captcha/api-key). That mismatch between declared requirements and runtime instructions is a discrepancy.
!
Instruction Scope
The runtime instructions tell the user/agent to download a script from raw.githubusercontent.com into /usr/local/bin and to read/store API key in ~/.config/2captcha/api-key or TWOCAPTCHA_API_KEY. The SKILL.md expects reading the user's config/env for the API key (not declared in metadata). The instructions also include example JS for injecting tokens into web pages (expected for automation). There are no instructions that obviously exfiltrate unrelated data, but the agent instructions do direct reading of a user config path and environment variables that were not declared.
!
Install Mechanism
Installation is a one-line curl from raw GitHub to /usr/local/bin and chmod +x. Downloading and installing a remote script into a system path is higher-risk than an instruction-only skill: it writes executable code on disk and may require elevated privileges. The source (raw.githubusercontent.com) is a common host but still represents executing remote code; the skill metadata contains no install spec or checksum to verify authenticity.
!
Credentials
Functionality legitimately requires a 2Captcha API key and a local config file or env var, but the skill metadata did not declare any required credentials or primaryEnv. That omission could mislead users/agents about what secrets are necessary. Beyond the API key, no unrelated credentials are requested, so the scope of secrets is limited — the issue is the missing declaration and the skill reading a user config path.
!
Persistence & Privilege
The skill does not set always:true and does not request broad platform privileges, which is good. However the provided install steps create an executable at /usr/local/bin and a config file under ~/.config/2captcha — both are persistent changes to the system. Installing a remote script into a system-wide bin is a privilege-sensitive operation and should be done with caution (inspect the script, avoid running as root blindly).
What to consider before installing
This skill appears to be a straightforward CLI for the 2Captcha service, but there are a few things to consider before installing or using it: - The SKILL.md/README expect you to provide a 2Captcha API key (TWOCAPTCHA_API_KEY or ~/.config/2captcha/api-key), but the registry metadata did not declare any required credentials — be aware the agent or scripts will look for that key in your env or config file. - The install instructions ask you to curl a script from raw.githubusercontent.com and write it to /usr/local/bin. Downloading and installing a remote script is risky: inspect the script contents on GitHub (or clone the repo) before running it, verify commit/release history, and avoid piping remote code to a privileged install. Prefer a package manager or verified release if available. - Installation will create persistent files (/usr/local/bin/solve-captcha and ~/.config/2captcha/api-key). Ensure you understand and consent to these changes. Do not run the install commands with sudo unless you trust the source and have inspected the code. - The skill is designed to assist automation that may be used to create accounts or bypass site protections. Consider legal, ethical, and terms-of-service implications for your intended use. If you want to proceed: review the solve-captcha script on the linked GitHub repo, confirm checksums or a tagged release, and only then install. If you expect an agent to call this skill autonomously, ensure you are comfortable with the agent having the ability to run local commands that read your API key from the environment or config file.

Like a lobster shell, security has layers — review code before you run it.

automationvk97fsfa2gxe3y5rk0p33p6g1hh80bwf5captchavk97fsfa2gxe3y5rk0p33p6g1hh80bwf5clivk97fsfa2gxe3y5rk0p33p6g1hh80bwf5latestvk97fsfa2gxe3y5rk0p33p6g1hh80bwf5

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments