ClawHub
Back to skill

Security audit

client-demo-portal

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent demo-portal guide, but it should be reviewed because customer or internal context may be sent to external AI/API services without clear handling limits.

Before installing, confirm that users understand which data stays in the local docs folder and which content may be sent to PatSnap MCP, DeepSeek, SerpAPI, or NewsAPI. Use non-sensitive demo data by default, keep API keys out of source control, and require customer or IT approval before sending internal documents or proprietary questions to external services.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Context-Inappropriate Capability

Medium
Confidence
91% confidence
Finding
The skill introduces an external DeepSeek API path that sends user questions and patent background context to a third-party LLM, even though the skill is framed as building a local client demo portal. This creates a real data-handling risk because local/customer content may be transmitted outside the claimed local environment without strong purpose limitation, consent flow, or data-classification guidance.

Intent-Code Divergence

Medium
Confidence
95% confidence
Finding
The IT Q&A says data is stored locally, but the skill also instructs sending context and queries to external APIs including DeepSeek and the MCP endpoint. That mismatch is dangerous because it can mislead operators or customers into believing sensitive material stays on-prem when it may actually leave the environment.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The documentation mentions local document storage and external API use, but it does not provide a clear user-facing warning about data handling implications. In context, this is risky because users may upload internal documents or use customer data during a demo without understanding that portions of the content or derived context could be sent to third-party services.

Static analysis

No suspicious patterns detected.