Back to skill

Security audit

Batch Content Plan

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent social media content-planning workflow with review-before-scheduling safeguards and no hidden executable behavior.

Before installing, understand that the skill may activate on broad planning phrases and may read brand/voice planning files to build social media calendars. Review generated calendars carefully before approving any scheduling handoff.

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
96% confidence
Finding

The trigger phrases include very generic requests such as "plan my content," "plan the week," and "fill my calendar," which overlap with ordinary assistant planning language. This can cause the skill to activate when the user did not intend to invoke this specific workflow, potentially pulling in connected-channel assumptions, reading brand artifacts, or steering the conversation into scheduling-related actions unexpectedly.

Content

No source excerpt is available for this finding.