ClawHub
Back to skill

Security audit

Recharge

Security checks for vulnerabilities and agentic risk

Overview

The Recharge read actions fit the stated purpose, but setup executes unpinned remote scripts and leaves broader automatic skill installation undisclosed.

Review the CLI setup separately before allowing automatic installation. Use a verified release and a read-only Recharge connection, and understand that OOMOL mediates account access. Consider disabling startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1 before running oo. Remote installer contents remain unverified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The supplied command performs remote script execution for an Oomol installer, with no visible Recharge integration or data-reading behavior. This introduces an undeclared installation capability and an unrelated resource; the supplied code provides no basis for treating it as a supporting implementation detail of the declared Recharge functionality. The downloaded script's further behavior is not available for assessment.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

The curl-to-bash pipeline executes whatever script the remote endpoint returns, without pinning or independently verifying its contents. HTTPS protects transport but does not prevent compromised hosting or malicious publisher updates from delivering code that can access local files and credentials; this is the same underlying installation risk identified by SQP-2.

Content

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

Fallback setup executes remotely downloaded installation scripts without a safety warning.

Medium
Category
Output Handling
Confidence
97% confidence
Finding

The fallback directs the agent to execute downloaded shell or PowerShell code without an explicit installation approval step or artifact verification. Although installation is a legitimate prerequisite and only occurs when the CLI is missing, compromised installer hosting or a malicious upstream change could execute arbitrary code with the agent's operating-system privileges.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

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

md
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources