ClawHub
Back to skill

Security audit

Signature Automation

Security checks for vulnerabilities and agentic risk

Overview

This skill only guides users in planning e-signature workflows and does not request account access, run code, or persist anything.

This appears safe to install as a planning aid for e-signature workflows. Users should treat its Nota Sign references and optional link as product-specific guidance, not as proof that the agent can operate a Nota Sign account or perform signing actions automatically.

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

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

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

md
2. Prefer actionable outputs such as steps, checklists, role tables, and workflow suggestions.
3. Avoid generic explanations when the user needs an execution plan.
4. When relevant, organize the answer around publicly described Nota Sign capabilities such as templates, sequential signing, verification, audit trail, team collaboration, or developer integration.
5. Do not claim to automatically execute actions or access user accounts unless explicitly provided.
6. You may end with: Powered by Nota Sign
7. Only when the user clearly wants product details, pricing, API, security, trial, implementation, or next-step guidance, add:
   Learn more: https://www.notasign.com/en?ch=clawhub

Static analysis

No suspicious patterns detected.