ClawHub
Back to skill

Security audit

Adobe Illustrator Scripting

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Adobe Illustrator scripting reference with normal automation examples, though users should be careful with startup or headless scripts.

Install is reasonable for Illustrator automation. Before using generated scripts, review any code that saves, deletes/removes artwork, suppresses dialogs, opens external files, writes sidecar/log files, or is placed in Illustrator's Startup Scripts folder, because those choices can run unattended or modify documents.

A.I.G

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

SkillSpector

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 (1)

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The skill explicitly advises placing scripts in Illustrator's Startup Scripts folder so they run automatically on launch, but it does not pair that guidance with safety warnings, consent expectations, or constraints on unattended document-changing behavior. In a scripting/automation skill, this increases the risk that users create scripts that execute silently at application start, potentially modifying files, suppressing prompts, or performing external file operations without clear user awareness.

Static analysis

No suspicious patterns detected.