Back to skill

Security audit

Gougoubi Market Orchestrator

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed Gougoubi workflow router, but it can hand off sensitive crypto-market actions from broad requests without requiring explicit confirmation.

Review this before installing if you use Gougoubi workflows with real funds or market authority. It should only be used when you intend an end-to-end Gougoubi operation, and the agent should ask for explicit approval before activation, liquidity staking, result submission, reward claiming, or recovery actions.

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)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The trigger examples are broad and map to generic conversational intents like 'check what is missing and continue' or 'handle this proposal end to end,' which can cause the orchestrator to activate in situations where a more specific skill or additional confirmation would be safer. In an orchestration skill that can route across proposal creation, activation, liquidity provision, result submission, reward claiming, or recovery, overbroad matching increases the risk of unintended operational actions from ambiguous user requests.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The description uses very broad routing criteria such as 'high-level' requests and workflows that 'span multiple stages,' which can cause the orchestrator to activate for loosely related crypto tasks. In an orchestration skill, overbroad activation increases the chance of misrouting users into sensitive market, reward, or recovery flows they did not explicitly intend, raising the risk of unintended financial or operational actions.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.