Back to skill

Security audit

GREEN-API

Security checks for vulnerabilities and agentic risk

Overview

This WhatsApp integration is coherent, but it needs Review because it exposes private-message and account-changing powers without clear confirmation or secret-handling safeguards.

Install only if you trust GREEN-API with the WhatsApp account data involved. Treat instance and partner tokens as secrets, avoid pasting real tokens into general chat when a safer secret store is available, and require explicit confirmation before sending, deleting, forwarding, reading histories, changing groups/settings, logging out, rebooting, or deleting instances.

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
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (4)

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · README.md (reported line 31)May include surrounding context.

md
{
  "mcpServers": {
    "green-api": {
      "url": "https://api.green-api.com/mcp"
    }
  }
}

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The README instructs users to provide a WhatsApp instance token directly in a natural-language prompt, which encourages disclosure of a sensitive credential to the agent and transit through connected systems. Without an explicit warning about secret handling, users may expose tokens in logs, chat history, telemetry, or to unintended tools, enabling unauthorized use of their GREEN-API instance.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill exposes privacy-impacting and potentially destructive WhatsApp capabilities such as reading chat history, accessing contacts, managing groups, and sending messages, but it does not instruct the agent to obtain user confirmation or warn about sensitive effects. In an agent setting, this increases the chance of unintended disclosure, unauthorized messaging, or actions taken on the wrong account or chat.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The tool list includes message deletion/editing, logout, reboot, instance deletion, group participant changes, and settings changes without any cautionary guardrails. Because these actions can irreversibly alter account state, communications, or configuration, omission of warnings and confirmation requirements creates a real risk of accidental or unauthorized destructive operations.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.