ClawHub
Back to skill

Security audit

Hologres Slow Query Analysis

Security checks across malware telemetry and agentic risk

Overview

This is a relevant Hologres troubleshooting guide, but it normalizes broad database privileges and full log exports without enough scoping or safety guidance.

Install only if you are comfortable manually reviewing database administration guidance. Prefer narrowly scoped read permissions, avoid SUPERUSER unless a database administrator explicitly approves it, treat exported query logs as sensitive data, and confirm any ALTER DATABASE, retention, or external export steps before running them.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Description-Behavior Mismatch

Medium
Confidence
93% confidence
Finding
The skill recommends granting SUPERUSER or broad statistics/log-reading privileges as part of normal setup, without enforcing least privilege or warning about the consequences. If followed casually, this can give an account unnecessary administrative visibility or control, increasing the blast radius of credential compromise or operator error.

Missing User Warnings

High
Confidence
97% confidence
Finding
The documentation explicitly instructs users to grant SUPERUSER or broad log/statistics access without any security warning, approval requirement, or least-privilege alternative. In a database operations context, this is especially dangerous because it normalizes privilege escalation during routine diagnostics and could expose all database logs or administrative capabilities to an account that does not need them.

Vague Triggers

Medium
Confidence
93% confidence
Finding
The trigger phrase "query diagnosis" is generic and can match many unrelated user requests, causing this skill to activate outside its intended Hologres-specific scope. Overly broad activation can route users into an inapplicable workflow, increasing the chance of incorrect guidance, accidental data exposure through unnecessary log analysis prompts, or interference with more appropriate skills.

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The document instructs users to export full contents from `hologres.hg_query_log`, including raw query text, usernames, application names, client metadata, plans, and error messages, without warning that these fields may contain secrets, personal data, or sensitive business logic. In a log-analysis skill this is contextually relevant, but it still increases the risk of unnecessary data exposure, over-collection, and propagation of sensitive information into less protected internal or external tables such as MaxCompute.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.