Back to skill

Security audit

Microsoft Clarity

Security checks for vulnerabilities and agentic risk

Overview

The skill is service-focused and mostly transparent, but its setup instructions tell an agent to execute an unverified remote installer if the CLI is missing.

Install only if you are comfortable with OOMOL mediating Microsoft Clarity access and avoid letting an agent run the remote installer automatically; install the oo CLI through a verified method and review payloads before any write-tagged action runs.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

The skill instructs the agent to install software using curl ... | bash, which downloads and immediately executes a remote script without integrity verification or pinning. In an adversarial or compromised distribution scenario, this can lead to arbitrary code execution on the host running the skill.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The activation text says to use this skill for ANY Microsoft Clarity request and instead of calling the API directly, which is overly broad and can cause the agent to invoke this skill whenever Clarity is merely mentioned. That increases the chance of unintended tool use and, in this skill, may cascade into shell command execution or connector operations without sufficiently narrow task matching.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.