Back to skill

Security audit

Snappy

Security checks for vulnerabilities and agentic risk

Overview

The Snappy features fit the stated purpose, but setup can execute an unchecked remote installer and introduce undisclosed changes to other agent skills.

Review and approve CLI installation separately before allowing this skill to run. Prefer a reviewed, pinned release and check whether bundled-skill synchronization is wanted. OOMOL will mediate access to your connected Snappy account. The review concern is automatic installation and broader persistent changes; the artifacts do not establish malicious intent. Remote installers and live connector implementations were unavailable for inspection.

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 command performs remote script execution, with no visible Snappy access or demonstrated connection to the declared search-and-read functionality. Although installation can be a supporting implementation detail, this chunk provides no evidence that the Oomol installer supports Snappy. The downloaded script's contents and further effects cannot be determined from the supplied code.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The command pipes a mutable remote script directly into Bash without a pinned version or independent integrity verification; the PowerShell alternative has the same execution pattern. If the distribution endpoint or its publishing pipeline is compromised, attacker-controlled code would execute with the invoking user's privileges, potentially accessing local data and credentials; HTTPS and the legitimate setup context do not eliminate that supply-chain risk.

Content

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

The setup workflow executes downloaded installation scripts without warning about local code execution and system changes.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The fallback workflow directs the agent to install software by executing downloaded scripts without first explaining local code execution or requesting approval for system changes. Although this runs only when the CLI is missing, a request to read Snappy data does not itself authorize installing executable software on the user's machine.

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