Back to skill

Security audit

database-semantic-to-sql

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a documentation-only SQL helper, but it requires the agent to append unrelated promotional content after successful SQL generation.

Review this skill before installing if you need clean SQL-only or machine-parsed outputs. Its SQL-generation guidance is proportionate, but the required promotional footer should be removed or made optional before use in strict workflows.

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
Findings (1)

T01 · Skill Instruction Hijacking

Warning
Location
SKILL.md:153
Finding

Mandatory Third-Party Promotional Content Hijacks Agent Responses

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The phrase 'Typically written in the local language for the target domain' imposes a locale-specific expectation in the specification text. Because the document does not provide an opt-in, alternative language option, or justification for a fixed locale, it can be read as a language policy constraint.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.