Back to skill

Security audit

Memos

Security checks for vulnerabilities and agentic risk

Overview

The Memos workflow requires approval for changes, but its CLI can also make lasting changes to other agent skills that this skill does not explain.

Review the CLI setup before allowing installation. Its documented startup synchronization can change other agent skill directories; setting OO_SKILLS_SYNC_DISABLED=1 before invoking oo disables that synchronization. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables) Use a reviewed CLI release, connect only the intended Memos account, and approve exact changes or deletions. Installer contents and hosted connector behavior remain unverified.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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
94% confidence
Finding

The supplied chunk performs remote software installation rather than the declared Memos data management. Installing a dependency could be a supporting implementation detail, but this chunk establishes no relationship between the Oomol installer and Memos. The downloaded script's contents are not supplied, so its additional behavior cannot be assessed.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
- `delete_attachment` — Delete one attachment by resource name. [destructive]
- `delete_memo` — Delete one memo, optionally forcing deletion when associated data exists. [destructive]
- `get_attachment` — Retrieve one attachment's metadata by resource name.
- `get_current_user` — Retrieve the Memos user associated with the connected personal access token.
- `get_memo` — Retrieve one memo by its Memos resource name.
- `get_user` — Retrieve one Memos user by resource name.
- `list_attachments` — List attachment metadata with pagination, filtering, and ordering.

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

The setup instructions pipe a remotely fetched script directly into Bash, and the Windows alternative similarly executes downloaded content without prior verification. Although installing a required CLI is legitimate and conditional, a compromised distribution endpoint or installer could execute arbitrary commands with the agent process's privileges; HTTPS does not independently establish artifact integrity.

Content

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

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