Back to skill

Security audit

voip-manager

Security checks for vulnerabilities and agentic risk

Overview

The skill is not clearly malicious, but it needs review because it asks for VoIP communication authority and an API key while using broad triggers and an absent referenced script.

Before installing, confirm which trusted VoIP service and script this is meant to run, provide the API key through protected secret handling, and require explicit user confirmation for placing, ending, or modifying calls.

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
95% confidence
Finding

The skill's activation criteria are broad enough to trigger on generic 'voice related functionality' and 'communication operations', which can cause the agent to invoke this skill in situations not clearly scoped to VoIP call management. Over-broad routing increases the chance of unintended access to call-related actions, misuse in adjacent contexts, or execution with insufficient user intent verification.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

The documentation instructs users to export a VOIP_API_KEY but provides no warning about treating it as a secret, avoiding logs/history exposure, or using secure secret storage. This can lead to accidental credential leakage through shell history, copied examples, debug output, or insecure environment handling, potentially enabling unauthorized access to the VoIP service.

Content

No source excerpt is available for this finding.