Back to skill

Security audit

Book Florist

Security checks for vulnerabilities and agentic risk

Overview

This florist booking skill is coherent and has no local code or persistence, but booking will involve sending contact details to an external service.

Before installing, be aware that using the booking flow may send your zip code and contact details to Lokuli or a florist provider. Only proceed when you intend to search or book a florist, and confirm booking details before submission.

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
  • 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)

Vague Triggers

Medium
Confidence
95% confidence
Finding
The trigger scope is broad enough to activate on essentially any florist-related request, which can cause the skill to engage in transactional behavior when the user may only be asking for general information. In this context, the skill can search and create bookings through an external MCP endpoint, so over-triggering increases the chance of unnecessary third-party data sharing or unintended booking flows.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
The skill documents a booking flow that transmits personal data including customer name, email, and phone number to an external service, but it does not clearly warn about that collection or obtain explicit user consent. In a booking skill, this omission is risky because users may not expect their contact information to be sent to a third-party provider merely from invoking the skill.

Static analysis

No suspicious patterns detected.