Back to skill

Security audit

clawec-shopee-product-search

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward Shopee product-search integration that sends search terms to Clawec with a user-provided API key, with no evidence of hidden persistence, destructive behavior, or unrelated data access.

Install this only if you are comfortable using Clawec for Shopee research: your search keyword, selected region, and Clawec API key will be sent to clawec.com. Use a dedicated API key if possible, avoid entering sensitive search text, and review Clawec's account and API terms before relying on the results.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (7)

Lp3

Medium
Category
MCP Least Privilege
Confidence
87% confidence
Finding
The skill documents shell-based execution (`curl` and `bash scripts/search.sh`) but does not declare any `permissions` or `allowed-tools` scope. This creates an authorization gap where an agent may invoke shell capabilities implicitly, making external network access and script execution less transparent and harder to constrain or review.

External Transmission

Medium
Category
Data Exfiltration
Content
## 调用

```bash
curl -s -X POST "https://www.clawec.com/api/aigc/ec/shopee_search" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $CLAWEC_API_KEY" \
  -d '{"keyword":"蓝牙耳机","region":"PH"}'
Confidence
84% confidence
Finding
The skill instructs the agent to send user-supplied search terms and an API bearer token to an external third-party endpoint. External transmission is expected for this skill’s purpose, but it is still a real security/privacy boundary because user input and credentials leave the local environment and are processed by an outside service.

External Transmission

Medium
Category
Data Exfiltration
Content
print(json.dumps(body))
' "$KEYWORD" "$REGION")

curl -s -X POST "https://www.clawec.com/api/aigc/ec/shopee_search" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $API_KEY" \
  -d "$PAYLOAD"
Confidence
70% confidence
Finding
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Missing User Warnings

Medium
Confidence
94% confidence
Finding
This shell script sends the user-supplied keyword and optional region to an external HTTPS API and authenticates with a sensitive environment variable, but the file provides no comment, echo/log message, or confirmation indicating that data will be transmitted off-host. For code files, outbound network transmission and use of credentials should have some visible disclosure unless clearly documented elsewhere, which is not present in this file.

Natural-Language Policy Violations

Low
Confidence
90% confidence
Finding
The markdown states '默认中文摘要', which imposes a specific language preference in the skill's behavior. Under the policy, language constraints should either be user-selected or clearly justified; this file does not present Chinese as an opt-in choice.

Natural-Language Policy Violations

Low
Confidence
88% confidence
Finding
This markdown file contains user-facing documentation only in Chinese, which can amount to a language-policy issue if users are not given a choice or informed that the skill is intentionally limited to that locale. The file does not indicate any opt-in, alternative language, or explicit justification for the language restriction.

Natural-Language Policy Violations

Low
Confidence
97% confidence
Finding
The usage and error strings are written only in Chinese, which imposes a specific language on all users of the skill. The file does not offer a language choice, fallback, or any justification that the skill is intended only for a Chinese-language or region-specific audience.

Static analysis

No suspicious patterns detected.