ClawHub
Back to skill

Security audit

HyperGrok Hyperliquid Websocket

Security checks for vulnerabilities and agentic risk

Overview

This skill is a read-only Hyperliquid WebSocket monitoring guide with disclosed background-watch examples and no bundled executable code or credential use.

Install this if you want Hyperliquid WebSocket monitoring guidance. Before running the watch examples, understand that they can keep a local process running, write logs under /workspace/trading-desk/watch, and record account activity for any address you configure.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Rogue AgentSelf-Modification, Session Persistence
  • 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
Findings (2)

Session Persistence

Medium
Category
Rogue Agent
Confidence
65% confidence
Finding

Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.

Content

Scanner excerpt · SKILL.md (reported line 80)May include surrounding context.

bash
mkdir -p /workspace/trading-desk/watch
nohup python3 /workspace/trading-desk/watch/ws_watch.py >> /workspace/trading-desk/watch/ws_watch.out 2>&1 &
echo $! > /workspace/trading-desk/watch/ws_watch.pid

Vague Triggers

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

The manifest description says "Use for monitoring, fill notifications and any watch that polling would make expensive," which describes a wide range of common monitoring situations but does not define specific activation phrases, scope limits, or exclusion conditions. In a manifest file, this kind of broad natural-language description can increase the chance of unintended invocation because it overlaps with many generic monitoring requests.

Content

No source excerpt is available for this finding.