Back to skill

Security audit

build-developer-faq-page

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward FAQ-writing assistant with no executable code, persistence, credential use, or hidden high-impact authority.

Installers should treat this as a content-generation helper and review any web-sourced or generated FAQ text before publishing, especially for product claims or customer-facing commitments.

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

Medium
Category
Not specified by scanner
Confidence
86% confidence
Finding

The invocation example "[Build Developer FAQ Page] for my team" does not define clear trigger constraints beyond a broad team-oriented phrase. The file also lacks negative examples or narrower activation conditions, which could cause unintended invocation during ordinary discussion about team FAQ work.

Content

No source excerpt is available for this finding.