Back to skill

Security audit

Maito

Security checks for vulnerabilities and agentic risk

Overview

This skill is a Maito workflow helper that uses authenticated Maito tools for newsletter, social, subscriber, analytics, and sponsor tasks with explicit approval gates for high-impact actions.

Install this only if you intend to let an agent work with your Maito workspace. Review connected Maito permissions because the skill can read or update newsletter, subscriber, analytics, and sponsor information, but its instructions require approval before externally visible or destructive actions.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 24)May include surrounding context.

md
3. Read current Maito state before creating duplicates or making changes.
4. If Maito is not connected, return a Maito-ready handoff instead of claiming persistence.

Do not ask the user for API keys by default. Maito login and MCP access should come from the connected client/session.

## Official Docs