Back to skill

Security audit

Hologres Query Optimizer

Security checks for vulnerabilities and agentic risk

Overview

The skill is a Hologres tuning guide, but it gives production database and persistent configuration commands without enough scoping or safeguards.

Review before installing. Use this skill only for Hologres work, install hologres-cli in an isolated pinned environment, and require explicit approval before running EXPLAIN ANALYZE, ANALYZE, table-property changes, or database-level GUC set/reset commands against production.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:11
Finding

Unpinned and Unverified Runtime Dependency Installation

Content
View full analysis
Remediation
View remediation
" ``` 2. Publish and verify cryptographic hashes for the package and all transitive dependencies. Use a requirements file with hash enforcement: ```bash python -m pip install --require-hashes -r requirements.txt ``` 3. Generate the requirements file from a trusted index and commit it to the Skill package so installations are reproducible. 4. Explicitly document the authoritative package source and configure the expected index URL. Avoid untrusted additional package indexes. 5. Re-audit the pinned dependency before updating it, including its release artifacts, installation hooks, transitive dependencies, and CLI runtime behavior. 6. Install and run the CLI in an isolated virtual environment or container under a least-privileged account. Do not expose unrelated credentials or sensitive environment variables to that environment. 7. Where supported, verify signed release provenance or other publisher attestations before installation. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The trigger list includes generic phrases like 'query plan', 'execution plan', 'sql optimization', and 'slow query' that are not scoped to Hologres. This can cause the skill to activate on unrelated SQL/database requests and deliver Hologres-specific advice or commands in the wrong context, increasing the chance of unsafe or incorrect operational guidance.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The documentation recommends executing EXPLAIN ANALYZE, ANALYZE, and GUC-setting commands and even states to 'Always use EXPLAIN ANALYZE for production analysis' without warning that these actions execute queries, consume resources, and may change database behavior. In a production environment, this can cause unintended load, locking/resource contention, or persistent configuration drift if an agent follows the guidance automatically.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger list contains generic phrases such as "query plan", "execution plan", "sql optimization", and "slow query" that are not scoped to Hologres. This can cause the skill to activate for unrelated database or general SQL requests, potentially intercepting prompts outside its intended domain and producing incorrect or overly authoritative guidance in the wrong context.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The documentation provides persistent database-level hologres guc set and reset commands that change optimizer and memory behavior for all users of the database, but it does not warn that these are shared, long-lived configuration changes. In a query-optimization skill, users may reasonably copy these commands directly, causing unintended performance regressions, outages, or cross-tenant impact if applied in production without scope, rollback, and approval guidance.

Content

No source excerpt is available for this finding.