Invoicy

• Outcome: Review
• Latest audit: May 29, 2026 at 9:31 PM UTC
• Version:
  1.0.0

Overview

This invoice tool appears purpose-aligned, but users should review it carefully because it stores sensitive invoice data and accepts SMTP passwords without clear handling or deletion terms.

Use only with invoice data you are comfortable sending to this external provider. Prefer test or limited app-specific SMTP credentials, confirm recipient and invoice contents before sending, avoid unnecessary bank or tax details, and verify the provider's retention, deletion, access-control, and credential-handling practices before production use.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (3)

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The skill explicitly supports emailing invoices via SMTP and accepts SMTP host, username, and password fields, but it provides no warning that invoice contents and mail credentials will be transmitted to external mail infrastructure. Because invoices commonly contain financial, tax, business, and contact data, users may unknowingly expose sensitive information or supply reusable email credentials to a third-party service.

Missing User Warnings

Medium

• Confidence: 85% confidence
• Finding: The overview states the service supports invoice lifecycle management and maintains invoice records for later retrieval, but it does not disclose retention, access controls, or handling of stored financial and personally identifiable information. This creates a real security/privacy risk because users may submit invoices containing tax IDs, banking details, addresses, and payment information without understanding that the service may persist them.

Missing User Warnings

Medium

• Confidence: 91% confidence
• Finding: The API exposes a send-email capability that accepts arbitrary SMTP host, username, and password fields, but the spec provides no warning, consent, or restrictions around transmitting invoice data to external mail servers or handling sensitive credentials. In an agent setting, this increases the risk of unintended data exfiltration, misuse of user-supplied SMTP secrets, and sending invoices to attacker-controlled infrastructure.

VirusTotal

64/64 vendors flagged this skill as clean.