ClawHub
Back to skill

Security audit

Alibaba Store Analysis

Security checks for vulnerabilities and agentic risk

Overview

This skill reads Alibaba store report data through the user's logged-in browser session for the stated purpose of producing store diagnostics.

Install only if you are comfortable letting the agent use your logged-in Alibaba session to retrieve weekly store analytics, report tokens, merchant tasks, and detailed business diagnostics. Avoid running it on accounts whose business metrics should not appear in the agent conversation.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Confidence
88% confidence
Finding
The skill explicitly states it uses an authenticated browser session to access Alibaba store report data and backend APIs, but it does not warn users that potentially sensitive business data will be retrieved and processed. This creates a meaningful privacy and informed-consent issue because users may not realize the scope of access granted once they authenticate, especially where report links, tokens, and detailed diagnostics are involved.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The workflow directs the agent to use the active browser session to make authenticated requests for store business data, but it does not require an explicit user-facing notice or consent step before accessing potentially sensitive account information. Because the data is pulled via session credentials and may include business diagnostics, metrics, and internal report tokens, this creates a privacy and authorization transparency issue if the user did not clearly intend that access at that moment.

Static analysis

No suspicious patterns detected.