Back to skill

Security audit

Eagle Doc

Security checks for vulnerabilities and agentic risk

Overview

The document workflow is coherent, but a missing dependency can trigger downloaded code execution without separate user approval.

Review and approve dependency installation separately, preferably using a pinned release with verified integrity. The downloaded installer was not available for inspection. Connect only the intended Eagle Doc account and confirm which financial documents will be uploaded through OOMOL.

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
95% confidence
Finding

The visible code installs external software rather than performing the declared Eagle Doc operations. Dependency installation could be a supporting implementation detail, but the supplied chunk provides no evidence that this installer supports Eagle Doc. The remote script's contents and any additional effects cannot be determined from this chunk.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

Piping the HTTPS response directly into Bash executes mutable remote content without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. OOMOL is a relevant dependency, but compromise of its distribution endpoint or release infrastructure could turn the fallback into arbitrary code execution with access to the user's files and locally available credentials.

Content

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

First-time setup executes remotely downloaded installation scripts without a system-integrity warning or explicit approval requirement.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The fallback directs the agent to install software by executing downloaded scripts without requiring explicit user approval for the local system changes. Although installation occurs only when the CLI is missing, an ordinary Eagle Doc request can therefore lead to execution of remote code with the invoking user's privileges, subject to tool permissions.

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