ClawHub

Database Tester

Security checks across malware telemetry and agentic risk

Overview

This is a legitimate database-testing skill, but it includes copyable SQL that can delete data or change server-wide MySQL settings without enough safety scoping.

Install only if you will use it against staging, local, or disposable databases with least-privilege test accounts. Treat DELETE, UPDATE, migration, deadlock, API mutation, and SET GLOBAL examples as actions requiring explicit review; avoid the server-wide MySQL logging commands unless an authorized DBA approves them in a controlled environment.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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 (3)

Description-Behavior Mismatch

Medium
Confidence
95% confidence
Finding
The skill explicitly says it is not for database administration, yet it instructs users to run `SET GLOBAL` commands that modify server-wide MySQL configuration. This is dangerous because it can change behavior for all clients on the database instance, require elevated privileges, and cause operational or compliance side effects outside the intended scope of a testing skill.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The examples include destructive SQL operations such as deleting a user and relying on cascade effects, but they are presented without a nearby warning to use disposable test data or a non-production environment. In a database-testing skill, users may copy these commands directly, risking accidental data loss or integrity changes in real systems.

Missing User Warnings

Medium
Confidence
96% confidence
Finding
Documenting `SET GLOBAL slow_query_log = 'ON'` and `SET GLOBAL long_query_time = 1` without warning omits that these are instance-wide configuration changes affecting all workloads. This can increase logging volume, alter performance characteristics, expose sensitive query text in logs, and violate the skill's own non-administration boundary.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal