Back to skill

Security audit

Speak 69378f

Security checks for vulnerabilities and agentic risk

Overview

This is a simple Markdown-only learning workflow skill with broad activation phrases but no executable behavior or sensitive access.

Install only if you want a lightweight Speak-related reference skill. Expect possible accidental activation from the common word "speak"; narrowing the trigger would improve usability, but no dangerous behavior was found in the artifact.

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger field includes very broad phrases such as "speak" and "Speak", which are common words likely to appear in ordinary conversation. This can cause unintended activation of the skill in unrelated contexts, increasing the chance of confusing behavior, incorrect routing, or accidental invocation of low-trust workflow content.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The activation scenarios are ambiguous because they allow invocation whenever a user says generic terms like "speak" or requests vaguely related help. In a conversational system this broad matching can be exploited or accidentally triggered by benign user input, causing unintended skill selection and reducing trust boundaries between unrelated tasks.

Content

No source excerpt is available for this finding.