Back to skill

Security audit

Ansible Ui

Security checks for vulnerabilities and agentic risk

Overview

The skill appears to be a placeholder DevOps CLI that overstates its capabilities and writes local command history, but I found no exfiltration, destructive behavior, or hidden remote execution.

Review this skill carefully before installing if you expect real Semaphore, Ansible, Terraform, or deployment automation. It appears low-risk from a malware perspective, but its documentation is misleading and the commands are mostly placeholders that write a local history log.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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 (6)

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

Presenting a placeholder CLI as a full-featured DevOps automation interface creates a trust mismatch that can mislead operators into using it in privileged environments. In security-sensitive DevOps contexts, undocumented no-op or stub behavior can hide missing controls, cause unsafe assumptions, and mask unexpected local side effects.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

Presenting a placeholder CLI as a full-featured DevOps automation interface creates a trust mismatch that can mislead operators into using it in privileged environments. In security-sensitive DevOps contexts, undocumented no-op or stub behavior can hide missing controls, cause unsafe assumptions, and mask unexpected local side effects.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

A generic command like 'help' can be triggered accidentally or conflict with common assistant workflows, increasing the chance of unintentional invocation of the skill. While low impact on its own, broad trigger names reduce user intent clarity and can become more dangerous when combined with command execution capabilities.

Content

No source excerpt is available for this finding.

Unrestricted Tool Access

Medium
Category
Excessive Agency
Confidence
94% confidence
Finding

The instruction to 'Run any command' indicates unconstrained command dispatch, which can expose powerful underlying tooling to arbitrary arguments without documented allowlists, guardrails, or confirmation boundaries. In a DevOps skill context, this is especially risky because commands may target infrastructure, credentials, state files, or local systems with significant operational impact.

Content

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

md
## Usage

Run any command: `ansible-ui <command> [args]`
---
💬 Feedback & Feature Requests: https://bytesagain.com/feedback
Powered by BytesAgain | bytesagain.com

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The manifest says the skill provides a modern UI and powerful API for tools like Ansible, Terraform/OpenTofu/Terragrunt, and PowerShell. In contrast, this script implements a simple local CLI that echoes placeholder status text for generic commands and appends command history to a local file, with no actual integration with those DevOps systems.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The help text presents commands such as 'Run checks', 'Build project', 'Run tests', 'Deploy guide', and 'Clean artifacts' as operational features. However, the corresponding command handlers do not perform those actions; they only echo descriptive text and log the invocation, which contradicts the user-facing documentation of what the commands do.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.