Security audit

azure-cli

Security checks across malware telemetry and agentic risk

Overview

This is a coherent Azure CLI reference skill with powerful but expected cloud-management examples that users should handle carefully.

Install this only if you want agent assistance with Azure administration. Use a least-privilege Azure identity, prefer a sandbox or non-production subscription for examples, confirm the active subscription and resource group before any create/update/delete/deploy/run-command action, and never share Azure tokens, connection strings, or service-principal secrets in chat or logs.

SkillSpector

By NVIDIA

Vulnerability Patterns

Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (5)

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The README includes commands that create billable Azure resources, deploy infrastructure, and execute remote shell commands on VMs, but it does not prominently warn users about costs, side effects, or that commands may modify or delete cloud assets. In a cloud-management skill, these examples are contextually expected, but omission of safety warnings still creates a real risk that users will run them verbatim and incur charges or alter production environments unintentionally.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The skill presents destructive Azure deletion commands as normal usage examples without an explicit warning about irreversible resource loss, attached dependencies, or possible production impact. In an infrastructure-management skill, users may copy-paste these commands directly, increasing the chance of accidental deletion of live cloud resources.

Missing User Warnings

Medium

Confidence: 93% confidence
Finding: The VM deletion example shows `az vm delete` with no user-facing caution that the operation is destructive and may remove a running workload or associated infrastructure. Because the document is instructional and action-oriented, this omission materially raises the risk of accidental execution against real environments.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The AKS deletion example omits a warning that deleting a cluster can cause immediate application outage, loss of cluster state, and disruption to dependent services. In the context of Azure administration, a simple copy-paste of this command could have substantial operational impact beyond a single resource.

Missing User Warnings

High

Confidence: 98% confidence
Finding: The batch operation example pipes all VM IDs in a resource group directly into `az vm delete`, enabling mass deletion with minimal friction and no strong warning or safety checks. This is especially dangerous because it scales accidental harm across an entire environment and is presented as a reusable pattern, making misuse more likely.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.