Refund Radar

• Outcome: Pass
• Latest audit: May 27, 2026, 9:17 PM
• Version:
  1.0.1

Overview

Refund Radar is a coherent local bank-statement audit skill, but users should treat its reports and templates as sensitive financial data.

Use this only on a trusted device, keep generated HTML/JSON reports private, delete ~/.refund_radar data when finished, avoid sharing full card or account numbers in templates, and verify the external Python module or repository before running it on real bank statements.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (3)

Vague Triggers

Medium

• Confidence: 89% confidence
• Finding: The trigger phrase on this line is broad enough to match ordinary user requests about reviewing financial transactions, which can cause the skill to activate when the user did not explicitly intend to invoke it. In a finance-related skill that processes sensitive bank statement data, accidental activation increases privacy and consent risk because users may be prompted to share or process highly sensitive financial information unexpectedly.

Vague Triggers

Medium

• Confidence: 86% confidence
• Finding: This trigger is also too generic for reliable routing and could overlap with normal conversational requests about suspicious charges or transaction review. Because the skill handles financial records and generates reports from sensitive statement data, unintended invocation could expose users to unnecessary data collection prompts or execution of local analysis on confidential inputs.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The file instructs users to include personal contact details and partial payment-card information in refund and dispute templates, but provides no guidance on safe transmission or data minimization. In a financial workflow, this increases the chance that users will paste sensitive information into insecure channels such as email or chat, leading to unnecessary exposure of personal and account data.

VirusTotal

66/66 vendors flagged this skill as clean.