Back to skill

Security audit

Asana

Security checks for vulnerabilities and agentic risk

Overview

The Asana workflow is coherent, but its fallback setup executes mutable downloaded code without clear approval or limits on local changes.

Review setup before installing. Approve a verified CLI release and control its automatic skill synchronization before allowing installation. OOMOL will mediate your Asana data and credentials, so connect an appropriately limited account. Keep the required confirmations for changes and deletions. The remote installers and hosted implementation were not verified; no malicious payload was 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 (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The declared purpose is Asana data management, but the supplied code only executes an installer from a different service. Dependency installation can be a supporting implementation detail, but this chunk provides no evidence that the installer supports Asana or implements the declared functionality. 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 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. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from serving malicious code, which could access local data and credentials under the executing user's permissions.

Content

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

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

Medium
Category
Output Handling
Confidence
94% confidence
Finding

When the CLI is missing, the setup workflow directs the agent to execute a remote installer without requiring explicit approval for local code execution or system changes. Although installation is relevant to the skill, the Asana write-confirmation rules do not clearly cover this host-level operation, which could execute compromised installer code with the agent process's 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 176)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