Security audit
Security checks for vulnerabilities and agentic risk
This skill is a straightforward Ozon product-search helper that sends user-provided keywords to the disclosed ClawEC API using a user-supplied API key.
Install only if you are comfortable sending searched keywords to ClawEC and using a ClawEC API key from your environment. Do not put secrets in commands or files, and review ClawEC's service terms and data handling if the keywords reveal sensitive business plans.
The skill demonstrates shell execution via curl/bash but does not declare any tool scope or allowed-tools restrictions. This increases the attack surface because an agent may invoke shell unexpectedly or more broadly than intended, making command execution harder to govern and audit.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -s -X POST "https://www.clawec.com/api/aigc/ec/ozon_search" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $CLAWEC_API_KEY" \
-d '{"keyword":"蓝牙耳机"}'
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
PAYLOAD=$(python3 -c 'import json,sys; print(json.dumps({"keyword": sys.argv[1]}))' "$KEYWORD")
curl -s -X POST "https://www.clawec.com/api/aigc/ec/ozon_search" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $API_KEY" \
-d "$PAYLOAD"
This code performs an HTTP POST and attaches a bearer token from the CLAWEC_API_KEY environment variable, but the script provides no visible notice, logging, or comment explaining that it will transmit data to an external service using credentials. For code files, outbound network calls and credential usage should have some user disclosure unless clearly documented elsewhere, which is not evident in this file.
The markdown states '默认中文摘要' (default Chinese summary), which imposes a language preference in the skill behavior. Under the policy, language constraints should either be user-selectable or clearly justified as region-specific; this file does not provide such an opt-in or justification.
This markdown file is natural-language documentation, and all headings and field descriptions are presented only in Chinese. Under the policy, forcing a specific language without user opt-in can be a language/locale policy violation when no justification or alternative is provided.
The usage and environment-variable error messages are hard-coded in Chinese, which imposes a specific language on all users. The policy allows locale constraints only when users can opt in or when the restriction is clearly documented and justified, neither of which is shown here.