Back to skill

Security audit

GI Database Query Patterns

Security checks for vulnerabilities and agentic risk

Overview

This is a database-query guidance skill with no executable code, installation side effects, hidden behavior, or persistence.

Before installing, users should know this skill is tailored to tkms AsyncSqlSessionTemplate and MySQL DAO work. It may be less appropriate for projects using different database libraries, and users may want to ask for responses in their preferred language if needed.

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)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

The skill title and body are presented in Chinese and line L009 states usage constraints in Chinese, with no indication that the user may choose another language. This can violate language or locale policy when a skill implicitly requires a specific language without opt-in or documented justification.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger conditions are broad enough to match many ordinary software-development requests such as writing DAOs, database operations, or table queries. This can cause the skill to activate in contexts where it was not specifically intended, increasing the chance of inappropriate routing, over-application of database-specific guidance, or accidental exposure of privileged implementation patterns across unrelated tasks.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.