ClawHub
Back to skill

Security audit

Cashclaw Core

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed business workflow coordinator that stores client mission records and sends business communications as part of its stated purpose.

Install only if you want CashClaw to manage client work, local business records, and client-facing messages. Review client data before it is saved, confirm recipients before any invoice or deliverable is sent, and periodically delete old ~/.cashclaw records you no longer need.

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Rogue AgentSelf-Modification, Session Persistence
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (3)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill instructs the agent to persist client requests, mission details, and business records under ~/.cashclaw without any consent, retention limits, minimization rules, or privacy notice. Because client requests may contain personal, financial, or business-sensitive information, this creates unnecessary long-term exposure if the host is shared, compromised, or later accessed by other tools.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
The skill authorizes outbound communications such as payment links, invoices, reminders, and deliverables to clients, but it does not require confirmation, recipient validation, or warning about external data sharing. This can cause unintended disclosure of client data or accidental messages to the wrong recipient, especially when combined with automated workflow delegation.

Session Persistence

Medium
Category
Rogue Agent
Content
When a new client request arrives:

1. Parse the client message for: service type, scope, deadline, budget hints.
2. Create a mission file at `~/.cashclaw/missions/MISSION-{YYYYMMDD}-{SEQ}.md`.
3. Log the intake in `~/.cashclaw/ledger.jsonl` with status `intake`.
4. Identify which CashClaw skill(s) are needed.
5. Ask clarifying questions if scope is ambiguous. Never assume; always confirm.
Confidence
94% confidence
Finding
This is a true session-persistence issue because the skill explicitly creates mission files and appends ledger entries for each client request, establishing durable memory outside the current interaction. In this business-orchestration context, persistent storage increases risk because the stored content can include client identities, raw requests, deadlines, pricing, and payment state, none of which are bounded by access controls or lifecycle management in the skill.

Static analysis

No suspicious patterns detected.