ClawHub
Back to skill

Security audit

go-lovable

Security checks for vulnerabilities and agentic risk

Overview

This skill is a documented Go client integration for the Lovable API, with credential and write/delete risks disclosed and tied to user-requested project management tasks.

Install only if you intend to use a Go client for Lovable. Use a Lovable API key with the narrowest practical scope, keep it in environment variables, avoid logging request headers or embed URLs, and confirm the exact workspace/project before running update, delete, publish, unpublish, or embed URL operations.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 31)May include surrounding context.

md
- Use `https://api.lovable.dev` as the base URL. Generated paths already contain `/v1`.
- API keys belong to one workspace and have project or workspace read/write scopes. Write scopes include their corresponding read scope. A different workspace's resource returns 404, and insufficient scope returns 403.
- Updating or deleting projects, changing publishing settings, publishing, unpublishing and creating embed URLs affect account resources or access. Perform those operations only when the user requested them.
- Embed URLs contain an access token. Treat them as credentials and share them only with the intended recipient.

## When to use

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/setup.md (reported line 36)May include surrounding context.

md
| `ListProjectsWithResponse` | `GET /v1/projects` |
| `GetProjectWithResponse` | `GET /v1/projects/{project_id}` |
| `UpdateProjectWithResponse` | `PATCH /v1/projects/{project_id}` |
| `DeleteProjectWithResponse` | `DELETE /v1/projects/{project_id}` |
| `CreateEmbedUrlWithResponse` | `POST /v1/projects/{project_id}/embed-url` |
| `PublishProjectWithResponse` | `POST /v1/projects/{project_id}/publish` |
| `UpdatePublishSettingsWithResponse` | `PATCH /v1/projects/{project_id}/publish` |

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/setup.md (reported line 40)May include surrounding context.

md
| `CreateEmbedUrlWithResponse` | `POST /v1/projects/{project_id}/embed-url` |
| `PublishProjectWithResponse` | `POST /v1/projects/{project_id}/publish` |
| `UpdatePublishSettingsWithResponse` | `PATCH /v1/projects/{project_id}/publish` |
| `UnpublishProjectWithResponse` | `DELETE /v1/projects/{project_id}/publish` |
| `GetDeploymentWithResponse` | `GET /v1/projects/{project_id}/publish/{deployment_id}` |
| `ListPiiLabelsWithResponse` | `GET /v1/projects/{project_id}/pii-labels` |
| `ListSecurityScansWithResponse` | `GET /v1/projects/{project_id}/security-scans` |

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
81% confidence
Finding

This markdown file documents write and delete operations such as updating projects, deleting projects, publishing, and unpublishing, but it does not include a user-facing warning that these actions can change or remove project state. Under the markdown-file criteria for missing user warnings, behaviors that can affect user data or system integrity should be accompanied by an explicit warning.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.