ClawHub
Back to skill

Security audit

Uuid Generator Tool

Security checks for vulnerabilities and agentic risk

Overview

This is a small UUID utility with disclosed, purpose-aligned behavior and no evidence of hidden network, persistence, credential, or destructive activity.

Installers should prefer UUID v4 for general identifiers. Use UUID v1 only when its timestamp and host-identifying metadata are acceptable for the place the UUID will be stored or shared.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The documentation promotes UUID v1 generation but does not warn that v1 embeds timestamp information and typically node/MAC-derived host identifiers. In a utility skill whose purpose is generating identifiers, users may unknowingly expose device or environment metadata if they use v1 in logs, URLs, or shared records, creating a real privacy and correlation risk.

Natural-Language Policy Violations

Low
Confidence
81% confidence
Finding
The manifest sets `language: en`, which imposes a specific language selection, yet the file itself includes a Chinese section later in the document. This creates a natural-language policy concern because the skill appears to force one locale rather than explicitly offering user choice or documenting a justified locale restriction.

Static analysis

No suspicious patterns detected.