ClawHub
Back to skill

Security audit

Abyssale

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly coherent for operating Abyssale through OOMOL, but its fallback setup tells an agent to run a remote installer script directly in a shell.

Review the oo CLI installation path before installing. Prefer installing the CLI from official documentation with verification where available, and make sure the agent asks before creating projects, generating banners, or changing Abyssale state.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • 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)

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

The skill instructs the agent to install software by piping a remotely fetched script directly into a shell (curl ... | bash), which is a classic supply-chain and remote code execution risk. If the remote host, CDN, transport path, or installer is compromised, arbitrary code would run immediately on the user's machine with the user's privileges.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The invocation text says to use this skill for ANY Abyssale request and instead of calling the API directly, which is overly broad and can cause the agent to route all Abyssale-related tasks through this skill without tighter scope checks. In an agent setting, broad trigger language increases the chance of unintended tool use, including write actions, when a narrower read/write distinction or explicit user confirmation should apply.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.