Back to skill

Security audit

clawec-amazon-best-seller

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed ClawEC API integration for Amazon bestseller lookup, with limited outbound data and no persistence or hidden local behavior found.

Install only if you are comfortable using a third-party ClawEC API key and sending the selected Amazon category value to clawec.com. Prefer setting CLAWEC_API_KEY in your environment rather than pasting or hardcoding it, and validate category names against the documented allowlist before calling the helper script.

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
93% confidence
Finding
The skill explicitly instructs use of shell commands (`curl`, `bash scripts/rank.sh`) but does not declare any tool scope such as `permissions` or `allowed-tools`. This creates an authorization gap where an agent may execute shell/network-capable actions without an explicit least-privilege boundary, increasing the chance of unintended command execution or broader environment access.

External Transmission

Medium
Category
Data Exfiltration
Content
**不限类目(默认):**

```bash
curl -s -X POST "https://www.clawec.com/api/aigc/tool/amazon_best_seller" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $CLAWEC_API_KEY" \
  -d '{"cat":""}'
Confidence
88% confidence
Finding
The skill sends data and an authorization bearer token to an external third-party API endpoint. External transmission is expected for this integration, but it still carries security risk because secrets are used in outbound requests and any user-provided category or derived data leaves the local trust boundary.

Natural-Language Policy Violations

Medium
Confidence
89% confidence
Finding
This markdown file uses Chinese exclusively for headings, field descriptions, and usage guidance, which can amount to a language policy violation if the organization expects skills to avoid forcing a specific language without user opt-in. There is no indication that the skill is region-specific or that users can choose another language.

External Transmission

Medium
Category
Data Exfiltration
Content
PAYLOAD=$(python3 -c 'import json,sys; print(json.dumps({"cat": sys.argv[1]}))' "$CAT")

curl -s -X POST "https://www.clawec.com/api/aigc/tool/amazon_best_seller" \
  -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
93% confidence
Finding
This code performs an HTTP POST to a third-party domain and includes both the user-supplied category payload and a bearer token from an environment variable. There is no prompt, logging, comment, or surrounding documentation in this file disclosing that data will be transmitted externally.

Natural-Language Policy Violations

Low
Confidence
95% confidence
Finding
The markdown instructs the skill to produce a '默认中文摘要', which imposes a specific language preference without asking the user or documenting an opt-in. This matches the policy category for language or locale constraints applied across any file type.

Natural-Language Policy Violations

Low
Confidence
95% confidence
Finding
The error text for a missing API key is hardcoded in Chinese ("请设置环境变量 CLAWEC_API_KEY"), which imposes a specific language on users regardless of their locale. No opt-in, alternative language, or documented region-specific justification is present in the file.

Static analysis

No suspicious patterns detected.