Back to skill

Security audit

Figma Design Brief

Security checks for vulnerabilities and agentic risk

Overview

This is a simple template skill for drafting Figma design briefs and does not request risky access or hidden actions.

Installers should expect this skill to help draft structured Figma design briefs from product requirements. Review the generated brief for product accuracy and consider invoking it explicitly when needed, since one trigger phrase is broad enough to match normal design-planning language.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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)

Vague Triggers

Low
Category
Not specified by scanner
Confidence
81% confidence
Finding

The example trigger phrase "Brief the designer on what to build for [requirement]" is relatively broad natural language that could plausibly appear in everyday product or design discussion, making unintended activation more likely. The file provides example triggers, but it does not include exclusion conditions or constraints clarifying when this skill should not activate.

Content

No source excerpt is available for this finding.