Back to skill

Security audit

Qase

Security checks for vulnerabilities and agentic risk

Overview

The skill is a mostly clear Qase connector, but its setup instructions include executing an unverified remote installer, so it should be reviewed before use.

Before installing, review or replace the remote installer path with a safer package-managed or verified install method. Use the skill only with an OOMOL/Qase account you intend the agent to access, and require clear approval before any create, update, complete, or destructive Qase operation.

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

The skill instructs the agent to install software using a remote script piped directly into a shell (curl ... | bash), which executes unverified code from the network without integrity checking or review. If the remote server, transport path, or published script is compromised, this becomes arbitrary code execution on the host running the skill.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The description says to use this skill for ANY Qase request and instead of calling the API directly, which is an overly broad trigger that can cause the agent to invoke this skill in situations where narrower tooling or additional policy checks would be more appropriate. In a skill that supports read, write, and destructive actions, broad invocation text increases the chance of unintended state-changing operations being routed through this path.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.