Back to skill

Security audit

Medical Billing & Revenue Cycle

Security checks for vulnerabilities and agentic risk

Overview

This is a medical billing guidance skill that asks for expected business metrics, with no hidden code or persistence, but users should avoid sharing patient-identifying data.

Install is reasonable for revenue-cycle and billing analysis use. Before using it, share only aggregated or de-identified information; do not paste PHI, patient names, claim numbers, member IDs, full contracts, credentials, or other sensitive records unless your organization has approved that workflow.

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

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill explicitly asks users to provide specialty, payer mix, KPIs, and problem areas in a healthcare revenue-cycle context without any minimization, de-identification, or privacy-handling guidance. While this is operational rather than directly clinical data, it can still expose sensitive business information and may encourage users to paste regulated or adjacent protected information into an AI system without safeguards.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.