ClawHub
Back to skill

Security audit

Hackathon Lovable

Security checks for vulnerabilities and agentic risk

Overview

This is a Markdown-only quick-start guide for building clinical hackathon apps in Lovable, with no executable code or hidden authority.

Installers should understand this skill as Lovable/OpenClaw hackathon build guidance, not medical, legal, HIPAA compliance, diagnosis, or treatment advice. It would be better if the skill narrowed its trigger language to Lovable or hackathon app-building requests, but the inspected artifact does not show malicious or Review-level behavior.

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

Vague Triggers

Medium
Confidence
90% confidence
Finding
The metadata description activates on broad phrases like 'clinical app' and 'quick-start guidance for clinical projects,' which can match ordinary healthcare requests outside the intended OpenClaw/Lovable niche. This can cause inappropriate skill routing, leading the agent to give platform-specific build guidance in contexts where it is irrelevant or unsafe for the user's actual need.

Vague Triggers

Medium
Confidence
91% confidence
Finding
The 'When to apply' section uses ambiguous conditions like 'clinical project' and 'quick start,' without firm boundaries or exclusions. In a healthcare context, overbroad triggering is more dangerous because it can misroute sensitive or regulated user requests into generic app-building guidance, increasing the risk of irrelevant, unsafe, or non-compliant assistance.

Static analysis

No suspicious patterns detected.