Back to skill

Security audit

Hugging Face

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly a disclosed Hugging Face connector, but it needs review because it routes broad Hugging Face requests through OOMOL and recommends unverified remote installer execution.

Install only if you intentionally want Hugging Face requests handled through OOMOL. Avoid sending secrets, regulated data, or sensitive prompts unless you accept that connector data path. Prefer a verified or package-manager install for the oo CLI instead of piping remote scripts directly into a shell.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Findings (2)

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:65
Finding

Unverified Remote Installation Scripts Executed Directly by Shells

Content
View full analysis
): ```bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux ``` ```powershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell ``` ``` ### Technical Analysis The installation instructions retrieve mutable scripts from `cli.oomol.com` and immediately execute them through Bash or PowerShell. Neither installation path pins the downloaded artifact to a reviewed version nor verifies a cryptographic checksum or digital signature before execution. The effective code executed on the host is therefore not contained in the audited Skill. It can change independently after review. Compromise of the distribution server, DNS or TLS trust infrastructure, deployment pipeline, or OOMOL account controlling the scripts could cause arbitrary attacker-controlled code to be returned. Although installation is presented as a fallback for a missing CLI, executing a remote response directly in a shell is not the minimum privilege necessary to install a command-line utility safely. ### Attack Path 1. The agent attempts to run an `oo` command and receives an `oo: command not found` error. 2. The Skill directs the user or agent to execute the platform-specific installation command. 3. The command downloads the current script from `cli.oomol.com`. 4. The response is passed directly to Bash or PowerShell without inspection or integrity verification. 5. A compromised or malicious response executes with the privileges of the invoking user. 6. The payload can access user-readable data, alter files, install additional software, or establish persistence where the invoking account has permission. ### Impact Assessment Successful expl ...[truncated 600 chars]
Remediation
View remediation

T01 · Skill Instruction Hijacking

Warning
Location
SKILL.md:3
Finding

Mandatory Third-Party Routing Expands Exposure of Hugging Face Request Data

Content
View full analysis
" ``` ```bash oo connector run "huggingface" --action "" --data '' --json ``` ### Technical Analysis The Skill instructs the agent to use it for every Hugging Face request and explicitly prohibits direct use of the Hugging Face API. It then transmits action names and JSON request payloads through OOMOL's connector infrastructure. Intermediation may be necessary when a user deliberately chooses an OOMOL-managed account, but requiring it for all Hugging Face tasks exceeds the minimum trust boundary required for public searches, metadata reads, and requests that could be performed directly. For inference actions, the JSON payload may contain prompts, conversation content, embedding inputs, model identifiers, or other user-supplied information. The document discloses that OOMOL is involved and states that credentials are injected server-side; therefore, the audit did not identify direct exposure of raw Hugging Face tokens in local commands. Nevertheless, mandatory routing gives an additional service visibility into request content and metadata. The file does not state data-retention terms, logging behavior, payload sensitivity restrictions, or a direct-access alternative. ### Attack Path 1. A user ...[truncated 1404 chars]
Remediation
View remediation
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (4)

External Script Fetching

High
Category
Supply Chain
Confidence
95% confidence
Finding

The skill instructs users to install the CLI via curl ... | bash, which executes a remote script directly without independent verification. If the hosting domain, transport, or upstream script is compromised, this becomes an easy path to arbitrary code execution on the user's machine.

Content

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

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The manifest promises this skill is for 'searching and reading data', but the documented actions include generate_chat_completion and generate_embeddings, which are inference/generation capabilities outside simple read/search behavior. This mismatch can mislead a caller or orchestrator into invoking a more capable skill than intended, weakening least-privilege assumptions and user consent around model generation.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The instruction to use this skill for 'ANY Hugging Face request' is overly broad and encourages automatic invocation whenever Hugging Face is mentioned. In context, that broad routing increases the chance of unintended tool use, unnecessary credentialed access, and use of this connector when a direct answer or a narrower skill would be safer.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
76% confidence
Finding

The safety text says state-changing actions will be tagged [write] or [destructive], yet the action list includes untagged generation operations and no tags at all. While generation may not modify remote state, presenting non-read actions as effectively equivalent to harmless reads can cause under-review of actions that incur cost, process sensitive prompts, or trigger external model execution.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.