Back to skill

Security audit

Semantic Shield

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed API-based trust lookup service for AI skills and plugins, with no bundled code execution or hidden persistence found.

Before installing, users should understand this is an external SaaS dependency that requires a vendor API key and sends skill identifiers, provider names, and optional public skill URLs to the service. Do not submit private repositories, internal URLs, secrets, or source code through the validation endpoint.

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

The trigger 'Asks about skill security, compliance, or risk assessment' is broad and could overlap with many general discussions rather than a clear invocation boundary for this specific skill. Although the file includes some negative examples, this trigger lacks tighter scope or concrete constraints on when Semantic Shield should activate versus when a general informational response would be more appropriate.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.