huawei-cloud-swr-image-automation

• Outcome: Review
• Latest audit: Aug 26, 2026 · 9:50 AM UTC
• Version: 1.0.3

Overview

This skill is coherent for Huawei Cloud SWR automation, but it can create persistent image-sync and auto-deploy behavior that may affect live cloud workloads, so it belongs in Review before installation.

Install only if you intend to let an agent help manage Huawei Cloud SWR sync and deployment triggers. Use least-privilege temporary credentials, verify any hcloud installer before running it, test in non-production namespaces first, avoid all-push production triggers unless you have release controls, and require explicit review before creating sync configs, using override=true, or enabling CCE/CCI auto-deploy triggers.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration

Findings (9)

Vague Triggers

Medium

• Confidence: 83% confidence
• Finding: The trigger phrases are broad enough to match generic terms like 'auto deploy', 'trigger', or 'image replication', which can cause this high-impact cloud operations skill to activate for ambiguous requests. Misrouting a user into a skill that performs repository sync or deployment-trigger management increases the chance of unsafe guidance or accidental write actions in the wrong context.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The guide instructs users to download and immediately execute a remote shell script via curl | bash-style behavior, including a non-interactive '-y' mode that suppresses review and confirmation. This is dangerous because any compromise of the download source, transport chain, or script contents would result in arbitrary code execution on the user's machine with the user's privileges.

Missing User Warnings

Medium

• Confidence: 89% confidence
• Finding: The guide provides ready-to-run examples for creating auto-deploy triggers, including configurations that fire on every image push, but does not clearly warn that this can automatically roll out unreviewed or unstable images to running workloads. In an automation skill, omission of that deployment-impact warning increases the chance of accidental production changes or abuse if a repository is compromised.

Missing User Warnings

Medium

• Confidence: 80% confidence
• Finding: The manual sync examples show `--override=true` without a prominent warning that existing target-region images with the same tags may be replaced. In a container registry context, overwriting tags can silently change what downstream deployments pull, causing integrity and rollback problems if users do not understand the consequence.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: These verification steps create and delete SWR sync configurations, which are state-changing operations against real cloud resources. Without an explicit warning to use test repositories and confirm authorization, a user may unintentionally alter production replication behavior or overwrite artifacts.

Missing User Warnings

High

• Confidence: 96% confidence
• Finding: Trigger creation, update, and deletion can directly affect running CCE/CCI workloads by enabling automated image-based deployment changes. Omitting a strong warning and environment-scoping guidance increases the risk of accidental rollout changes, service disruption, or unexpected production updates.

Missing User Warnings

High

• Confidence: 98% confidence
• Finding: The end-to-end flow instructs users to push new images and wait for automatic deployment updates, which can change live runtime state if pointed at production repositories or clusters. Because it lacks strong guardrails, this verification sequence could trigger unintended releases, workload changes, or outages through normal operator misuse rather than an exploit chain.

Autonomous Decision Making

Medium

• Category: Excessive Agency

Content

### W1: Create a Trigger

Set up auto-deploy to a CCE workload when new images are pushed:

**Pre-creation Checklist** (all steps are mandatory — skipping may result in misleading errors):
1. Verify repository exists:

• Confidence: 86% confidence
• Finding: This content explicitly instructs creation of SWR triggers that automatically update CCE/CCI workloads on new image pushes, enabling infrastructure changes without a human approval step at execution time. In a deployment automation skill, that behavior is expected, but it still creates a real security risk because a compromised image push, overly broad trigger condition, or mis-targeted workload can cause unintended or unauthorized production changes.

Autonomous Decision Making

Medium

• Category: Excessive Agency

Content

## Common Scenarios

### S1: CI/CD Auto-deploy Pipeline

Set up automatic deployment updates when CI pushes new images:

• Confidence: 83% confidence
• Finding: The CI/CD scenario normalizes automatic deployment on image push, including examples for staging and production, which can propagate a malicious or accidental image directly into running workloads. Although framed as operational guidance, it meaningfully lowers the barrier to high-impact autonomous changes in cluster environments.

VirusTotal

64/64 vendors flagged this skill as clean.

Static analysis

No suspicious patterns detected.