Back to skill

Security audit

Linkhut

Security checks for vulnerabilities and agentic risk

Overview

Review is recommended because setup can execute remote code without separate approval, and the CLI has broader effects on installed agent skills.

Review and verify the CLI installation before allowing the agent to perform setup. OOMOL mediates access to your Linkhut account. To prevent broader agent-skill changes, the current CLI documents setting OO_SKILLS_SYNC_DISABLED=1 before invocation; see its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Keep the explicit confirmations for bookmark changes. The remote installer and hosted connector implementations were not verified.

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
  • 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
97% confidence
Finding

The supplied code executes an Oomol-hosted installer rather than performing Linkhut operations. Nothing provided establishes that this installer is a supporting dependency for Linkhut. The fetched script's contents are not supplied, so its further effects cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping an HTTPS response directly into bash executes mutable remote content without an independent integrity check; the PowerShell alternative has the same trust issue. A compromised distribution endpoint or malicious installer update could execute code with the invoking user's privileges, potentially accessing local secrets or altering files. The endpoint is relevant to the dependency and setup is conditional, but neither fact verifies the downloaded code.

Content

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

Fallback setup executes downloaded installation scripts without warning about local system changes or remote-code execution.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The fallback directs installation after a missing-command error without requiring informed approval for executing remote code or changing the local system. Restricting setup to a genuine dependency failure reduces exposure, but the Linkhut write-confirmation rules do not cover this separate local installation side effect.

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 80)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