Azion Deploy

Security checks across malware telemetry and agentic risk

Overview

This skill is a clear Azion deployment helper, but users should treat it as a real publishing tool and review tokens, install steps, and deployment targets before running it.

Install only if you intend to deploy to Azion. Use the correct project directory and account, prefer least-privileged and well-protected Azion tokens, keep .env files out of version control, verify official Azion CLI installation methods before running remote install scripts, and confirm the deployment target before using quickstart or --auto.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (4)

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The documentation instructs users to install software by piping a remotely fetched script directly into a shell, with no integrity verification or warning. If the download server, CDN path, TLS trust chain, or upstream script is compromised, arbitrary code executes immediately on the user's machine.

Missing User Warnings

Medium
Confidence
88% confidence
Finding
The examples load secrets from .env and pass the token on the command line without warning about credential exposure. Tokens provided via shell environment or CLI flags can leak through shell history, process listings, CI logs, debugging output, or accidental repository inclusion of .env files.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The quickstart flow performs linking, building, and deployment immediately, including `azion link --auto` and `azion deploy --auto`, without any confirmation gate before changing remote state. In an agent context, this is risky because a user request to 'set up' or 'try' deployment could trigger a real publish operation to Azion using available credentials.

Missing User Warnings

Medium
Confidence
89% confidence
Finding
`deploy-local` supports `--auto` and then executes `azion deploy` directly, allowing unattended deployment with no warning at the point of action. In this skill's context, the script is specifically designed to deploy to a live platform, so exposing non-interactive state-changing behavior increases the chance of accidental or agent-driven publication using stored tokens.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal