Back to skill

Security audit

EnvelopeBudget

Security checks for vulnerabilities and agentic risk

Overview

The skill matches its EnvelopeBudget purpose, but it can modify live budget records without built-in confirmation safeguards.

Install only if you are comfortable giving the agent access to your EnvelopeBudget API key. Treat POST, PUT, PATCH, and DELETE calls as live changes to budget data, and require the agent to show the proposed change and get explicit approval before running them.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger description is extremely broad, including 'anything related to budgeting, expenses, or financial tracking,' which can cause the agent to invoke this skill for a wide range of finance-adjacent requests. In a skill that can read and modify live financial records, overbroad routing increases the chance of unintended access or state-changing actions in contexts where the user did not clearly request use of this specific integration.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The documentation includes examples for creating transactions and transferring funds between envelopes using live API endpoints, but it does not warn that these actions modify real budget data or require explicit user confirmation. In a financial context, missing safety guidance can lead to accidental writes, corrupted records, or unauthorized financial changes if the skill is invoked loosely or the agent acts on ambiguous prompts.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.