ClawHub
Back to skill

Security audit

remember-invoices

Security checks for vulnerabilities and agentic risk

Overview

This billing-memory skill has a coherent purpose, but it sends detailed customer and payment information to a fixed external service without enough consent, minimization, or retention guidance.

Install only if your organization approves sending invoice and customer billing records to BlueColumn's hosted service. Use narrowly scoped API keys, avoid uploading bank details, full contracts, or unnecessary prior messages, and confirm retention, deletion, access controls, and customer-data processing terms before using it with real billing data.

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
Findings (1)

other

Warning
Location
SKILL.md:15
Finding

Uncontrolled Disclosure of Sensitive Billing and Customer Data to a Third-Party Service

Content
View full analysis
Remediation
View remediation

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill explicitly instructs agents to send invoice details, client names, payment status, and payment channel information to an external endpoint, but it does not provide any user-facing warning, consent boundary, or data-minimization guidance. In a billing context this is sensitive financial/business data, so silently transmitting it to a third-party service creates confidentiality and compliance risk.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
97% confidence
Finding

The documented curl command sends detailed invoice metadata and payment information to an external Supabase-hosted endpoint using a live API key. Even if intended functionality is memory storage, this is still an external transmission of sensitive billing data, and in this skill's context the risk is heightened because the examples encourage sending full client-identifiable financial records.

Content

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

Store every invoice the moment it is issued: amount, client, due date, status, and the payment channel.

bash
curl -X POST https://xkjkwqbfvkswwdmbtndo.supabase.co/functions/v1/agent-remember \
  -H "Authorization: Bearer $BLUECOLUMN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "INVOICE INV-1042: $4,800 to Acme Corp, issued Jul 28, due Aug 27, status OPEN. Sent via Stripe; client pays by ACH.", "title": "invoice - INV-1042 Acme"}'

Static analysis

No suspicious patterns detected.