Back to skill

Security audit

Spider Cloud

Security checks for vulnerabilities and agentic risk

Overview

The Spider Cloud workflow is coherent, but its automatic setup can execute unverified installers and introduce broader, undisclosed changes to agent skills.

Review setup before enabling this skill. Install a verified, pinned CLI yourself and require approval for further software changes. Consider setting OO_SKILLS_SYNC_DISABLED=1 before invoking oo to prevent startup skill synchronization, as documented in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). OOMOL will mediate your Spider Cloud requests and credentials, and usage may incur charges. The remote installers remain uninspected; no malicious intent is established.

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 (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
99% confidence
Finding

The supplied command executes a remote installation script rather than performing Spider Cloud searches or data reads. Nothing in the supplied code establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents and further effects are not shown.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
88% confidence
Finding

The supplied chunk performs a CLI login rather than searching or reading Spider Cloud data. Authentication could be a supporting implementation detail, but nothing in this chunk establishes that oo authenticates to Spider Cloud.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The curl-to-bash pipeline executes a mutable remote script immediately, without a pinned version or independent integrity verification. Compromise of the distribution endpoint or release pipeline could therefore execute arbitrary commands with the invoking user's privileges; the documented OOMOL dependency explains the destination but does not remove this supply-chain risk.

Content

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

The setup fallback executes downloaded installation scripts without warning the user about remote code execution or system changes.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

The missing-CLI fallback directs installation through shell or PowerShell execution of downloaded code without requiring user approval or explaining possible system changes. Although conditional and potentially blocked by the declared oo-only tool permission, it creates an unsafe escalation from a data-retrieval task to local software installation wherever execution is permitted.

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