Back to skill

Security audit

Dynatrace

Security checks for vulnerabilities and agentic risk

Overview

The Dynatrace features fit their purpose, but setup directs the agent to execute changing third-party code without separate user approval.

Review the CLI installation separately before enabling automatic setup. Prefer a pinned, independently verified release and explicitly approve installation and any bundled-skill changes. Use narrowly scoped Dynatrace read permissions and understand that access runs through OOMOL. No malicious behavior was established, but the remote installer and its persistent effects could not be fully assessed.

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

The supplied command performs remote script execution for an apparent Oomol CLI installation, not Dynatrace searching or reading. No connection between this installer and the declared Dynatrace functionality is shown, so this is an undeclared capability rather than an established supporting implementation detail. The exact effects of the downloaded script cannot be determined from the supplied code.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

The command pipes a remotely fetched script directly into Bash without a pinned version or independent integrity verification; the PowerShell example uses the equivalent download-and-execute pattern. Compromise of the distribution endpoint or delivery pipeline could execute arbitrary code with the invoking user's privileges, exposing local files and credentials. The legitimate dependency and conditional setup do not remove this supply-chain risk, which overlaps with SQP-2.

Content

Scanner excerpt · SKILL.md (reported line 57)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
96% confidence
Finding

A missing CLI triggers instructions to execute remote installation code without first explaining the system changes or obtaining explicit installation approval. This expands a Dynatrace read request into local software installation; limiting setup to actual failures reduces exposure but does not establish user consent.

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