Back to skill

Security audit

GOG Cleanup Reminder

Security checks for vulnerabilities and agentic risk

Overview

This skill performs a clearly described personal GOG cleanup workflow, with disclosed email and Apple Reminders side effects.

Before installing, confirm the GOG library export and Himalaya account are the intended personal files, run the documented dry-run first, and only add the sample cron entry if you want recurring emails and reminders.

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
  • Behavioral ASTexec() Call, eval() Call, Dynamic Import
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Lp3

Medium
Category
MCP Least Privilege
Confidence
90% confidence
Finding
The skill invokes shell commands and reads local files but does not declare any explicit tool scope such as permissions or allowed-tools. That creates a trust and review gap: an agent may execute filesystem and command-line actions without a clearly constrained contract, increasing the chance of unintended file access, local command misuse, or broader execution than the user expects.

subprocess module call

Medium
Category
Dangerous Code Execution
Content
def run_command(cmd: List[str], input_text: Optional[str] = None) -> subprocess.CompletedProcess:
    return subprocess.run(
        cmd,
        input=input_text,
        text=True,
Confidence
70% confidence
Finding
subprocess module calls execute external commands. Without careful input validation, this enables command injection.

Static analysis

No suspicious patterns detected.