Back to skill

Security audit

Canny

Security checks for vulnerabilities and agentic risk

Overview

Canny actions have clear approval controls, but the CLI setup can introduce persistent changes to other agent skills that this skill does not disclose.

Review the CLI installation separately before letting an agent perform setup. Use a verified release and disable startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1 before CLI use if you do not want other agent skill directories changed. OOMOL mediates Canny access; confirm the connected account and each proposed write. The remote installers and hosted connector implementation 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
  • 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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (3)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The supplied code performs remote software installation, not the declared Canny functionality. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence connecting the Oomol installer to Canny. The remote 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 setup command executes a mutable remotely hosted script directly in a shell without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint could lead to arbitrary code execution with the invoking user's permissions, including access to local files and credentials. Its legitimate dependency-installation purpose and missing-CLI trigger limit exposure but do not remove the supply-chain risk.

Content

Scanner excerpt · SKILL.md (reported line 65)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 86)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