ClawHub
Back to skill

Security audit

Book Auto Body

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward auto-body search and booking helper that uses an external Lokuli MCP service and has no local code, persistence, or hidden install behavior.

Before installing, understand that searches and bookings use Lokuli's external MCP service. Only provide name, email, and phone when you intend to create a booking, and confirm the provider, service, time slot, and contact details before submission.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Missing User Warnings

High
Confidence
97% confidence
Finding
The skill defines a booking flow that transmits customerName, customerEmail, and customerPhone to an external MCP endpoint without any documented warning, consent step, or privacy notice. In this context, the omission is dangerous because users may provide sensitive contact information without understanding that it will be sent to a third-party booking provider.

Vague Triggers

Medium
Confidence
94% confidence
Finding
The trigger scope is broad enough to activate on vague requests like any auto-body service request, which can cause the skill to engage when the user did not clearly intend to use this third-party booking workflow. In context, that increases the chance of unnecessary data collection, external service queries, and unintended bookings through the Lokuli MCP endpoint.

Static analysis

No suspicious patterns detected.