Back to skill

Security audit

CPA — Client Document Chase

Security checks for vulnerabilities and agentic risk

Overview

This document-chasing guide needs review because it encourages contacting third parties about sensitive client records without checking client permission.

Confirm client permission, recipient identity, and allowed disclosures before contacting a spouse, bookkeeper, or other document holder. Use approved secure channels, and keep extension, incomplete-delivery, and disengagement decisions under practitioner control.

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
Vulnerability Patterns
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • 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)

The workflow directs contact with a separate document holder without warning about client confidentiality or checking authorization.

Medium
Category
Output Handling
Confidence
87% confidence
Finding

The workflow directs the agent to contact the actual document holder, explicitly including a spouse or bookkeeper, without first verifying that the client has authorized that contact and the associated disclosures. A document request can reveal the engagement, financial holdings, or missing tax information to an unauthorized third party; the sensitive CPA context makes this omission consequential, although no malicious destination or deliberate exfiltration is specified.

Content

No source excerpt is available for this finding.