Back to skill

Security audit

vmware-vks

Security checks for vulnerabilities and agentic risk

Overview

ClawScan marks this VKS management skill suspicious because it handles powerful credentials and the review of a referenced file was incomplete, despite its stated purpose appearing aligned with its capabilities.

Consider the suspicious verdict and incomplete scan before installing. In particular, review the unpinned installation command and treat any exported kubeconfig as sensitive access material; the scanners do not establish that the skill is malicious or that the partially inspected content is safe.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (99)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
name: vmware-vks
description: >
  Use this skill whenever the user needs to manage vSphere Kubernetes Service (VKS) — Supervisor clusters, vSphere Namespaces, and TKC cluster lifecycle.
  Directly handles: check VKS compatibility, create/delete namespaces, create/scale/upgrade/delete TKC clusters, get kubeconfig, check Harbor registry.
  Always use this skill for "create Kubernetes cluster", "scale workers", "upgrade K8s version", "create namespace", "get kubeconfig", or any VKS/TKC task.
  Do NOT use for vanilla VM operations (use vmware-aiops), non-vSphere Kubernetes (e.g., kubeadm, EKS, AKS), or AVI/AKO load balancing (use vmware-avi).
  For networking use vmware-nsx.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
description: >
  Use this skill whenever the user needs to manage vSphere Kubernetes Service (VKS) — Supervisor clusters, vSphere Namespaces, and TKC cluster lifecycle.
  Directly handles: check VKS compatibility, create/delete namespaces, create/scale/upgrade/delete TKC clusters, get kubeconfig, check Harbor registry.
  Always use this skill for "create Kubernetes cluster", "scale workers", "upgrade K8s version", "create namespace", "get kubeconfig", or any VKS/TKC task.
  Do NOT use for vanilla VM operations (use vmware-aiops), non-vSphere Kubernetes (e.g., kubeadm, EKS, AKS), or AVI/AKO load balancing (use vmware-avi).
  For networking use vmware-nsx.
installer:

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
| **Namespace** | List, get, create with quotas, update, delete with TKC guard, VM classes | 6 |
| **TKC Clusters** | List, get, versions, create, scale, upgrade, delete with workload guard | 7 |
| **VM Service** | VM snapshots, VM groups + bootOrder, VM multi-NIC readout (vm-operator CRDs, read-only) | 3 |
| **Access** | Supervisor kubeconfig, TKC kubeconfig, Harbor registry, storage usage | 4 |
| **Permissions** | Which account is in use and whether it holds each tool's vSphere privileges (read-only) | 1 |

## Quick Install

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
| **Namespace** | List, get, create with quotas, update, delete with TKC guard, VM classes | 6 |
| **TKC Clusters** | List, get, versions, create, scale, upgrade, delete with workload guard | 7 |
| **VM Service** | VM snapshots, VM groups + bootOrder, VM multi-NIC readout (vm-operator CRDs, read-only) | 3 |
| **Access** | Supervisor kubeconfig, TKC kubeconfig, Harbor registry, storage usage | 4 |
| **Permissions** | Which account is in use and whether it holds each tool's vSphere privileges (read-only) | 1 |

## Quick Install

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
- Check if vSphere environment supports VKS
- Create, update, or delete Supervisor Namespaces with resource quotas
- Deploy, scale, upgrade, or delete TKC (TanzuKubernetesCluster) clusters
- Get kubeconfig for Supervisor or TKC clusters
- Check Harbor registry info or storage usage

**Use companion skills for**:

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
| **VM Service** | `list_vm_service_snapshots` | Read |
| | `list_vm_service_groups` | Read |
| | `list_vm_service_network_interfaces` | Read |
| **Access** | `issue_supervisor_kubeconfig` | Write (credential) |
| | `issue_tkc_kubeconfig` | Write (credential) |
| | `get_harbor_info` | Read |
| | `list_namespace_storage_usage` | Read |

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
| | `list_vm_service_groups` | Read |
| | `list_vm_service_network_interfaces` | Read |
| **Access** | `issue_supervisor_kubeconfig` | Write (credential) |
| | `issue_tkc_kubeconfig` | Write (credential) |
| | `get_harbor_info` | Read |
| | `list_namespace_storage_usage` | Read |
| **Permissions** | `get_access_info` | Read |

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
r when any part of the blast radius could not be read. the old `confirmed` and `dry_run` aliases were removed in 3.4.2 and are refused as unknown arguments.

**Credential access**: `issue_supervisor_kubeconfig` and `issue_tkc_kubeconfig` are not reads. The kubeconfig embeds a Supervisor bearer token (JWT from `/wcp/login`) that acts as the configured vCenter account until it expires — typically hours, and not revoked when vmware-vks exits. So:
- Run them only when the user explicitly asks for a kubeconfig; never auto-run them or fetch one as a side step. Both are annotated `readOnlyHint: false` (MCP clients ask first) and `risk_level: medium` (so an operator's `min_risk_level: medium` deny rule covers them).
- Always pass `output_path` (MCP) or `-o <path>` (CLI) and report only the path. The file is created owner-only (0600) — also when it replaces an existing file — and a symlink target is refused. Delete it when no longer needed.
- The audit row records who fetched which kubeconfig,

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · evals/evals.json (reported line 17)May include surrounding context.

json
},
    {
      "id": 2,
      "prompt": "Scale the production TKC cluster to 5 workers and get me the kubeconfig",
      "expected_output": "Cluster scaled, kubeconfig written to a file",
      "files": [],
      "expectations": [

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · evals/evals.json (reported line 18)May include surrounding context.

json
{
      "id": 2,
      "prompt": "Scale the production TKC cluster to 5 workers and get me the kubeconfig",
      "expected_output": "Cluster scaled, kubeconfig written to a file",
      "files": [],
      "expectations": [
        "Uses scale_tkc_cluster with worker_count=5",

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · evals/evals.json (reported line 22)May include surrounding context.

json
"files": [],
      "expectations": [
        "Uses scale_tkc_cluster with worker_count=5",
        "Uses issue_tkc_kubeconfig with output_path to write the kubeconfig to a file",
        "Reports the file path and does not print the kubeconfig or its token"
      ]
    },

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · evals/evals.json (reported line 22)May include surrounding context.

json
"files": [],
      "expectations": [
        "Uses scale_tkc_cluster with worker_count=5",
        "Uses issue_tkc_kubeconfig with output_path to write the kubeconfig to a file",
        "Reports the file path and does not print the kubeconfig or its token"
      ]
    },

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · evals/evals.json (reported line 23)May include surrounding context.

json
"expectations": [
        "Uses scale_tkc_cluster with worker_count=5",
        "Uses issue_tkc_kubeconfig with output_path to write the kubeconfig to a file",
        "Reports the file path and does not print the kubeconfig or its token"
      ]
    },
    {

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/agent-guardrails.md (reported line 70)May include surrounding context.

md
## Skill routing

- vmware-vks: Supervisor status and compatibility, vSphere namespaces, VM
  classes, Tanzu Kubernetes clusters, kubeconfig retrieval, Harbor registry.
- vmware-monitor: read-only vCenter inventory, hosts, alarms, events. Prefer it
  for any question that only reads about the underlying vSphere estate.
- vmware-aiops: VM lifecycle for ordinary VMs, not Supervisor-managed ones.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/agent-guardrails.md (reported line 102)May include surrounding context.

md
## Credentials and writes in vmware-vks

- issue_supervisor_kubeconfig and issue_tkc_kubeconfig return credentials. Call
  them only when the user explicitly asks for a kubeconfig — never as a step
  you decided on yourself, and never to "check access".
- Never print a kubeconfig, session token or bearer token into the conversation.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/agent-guardrails.md (reported line 102)May include surrounding context.

md
## Credentials and writes in vmware-vks

- issue_supervisor_kubeconfig and issue_tkc_kubeconfig return credentials. Call
  them only when the user explicitly asks for a kubeconfig — never as a step
  you decided on yourself, and never to "check access".
- Never print a kubeconfig, session token or bearer token into the conversation.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/agent-guardrails.md (reported line 103)May include surrounding context.

md
## Credentials and writes in vmware-vks

- issue_supervisor_kubeconfig and issue_tkc_kubeconfig return credentials. Call
  them only when the user explicitly asks for a kubeconfig — never as a step
  you decided on yourself, and never to "check access".
- Never print a kubeconfig, session token or bearer token into the conversation.
  Always pass output_path (MCP) or -o (CLI) and report the path only.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/agent-guardrails.md (reported line 105)May include surrounding context.

md
- issue_supervisor_kubeconfig and issue_tkc_kubeconfig return credentials. Call
  them only when the user explicitly asks for a kubeconfig — never as a step
  you decided on yourself, and never to "check access".
- Never print a kubeconfig, session token or bearer token into the conversation.
  Always pass output_path (MCP) or -o (CLI) and report the path only.
- Storage policies are selected by Policy ID, not display name. Call
  list_supervisor_storage_policies and use the ID column.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/capabilities.md (reported line 13)May include surrounding context.

md
ompatibility`, `get_supervisor_status`, `list_supervisor_storage_policies`, `list_namespaces`, `get_namespace`, TKC list/get, `get_harbor_info`, `list_namespace_storage_usage` |
| **L2** | Read + analysis / recommendation | Always auto-run | namespace quota analysis, TKC health correlation, storage policy compatibility checks |
| **Credential** | Returns live access material (bearer token) | **Never auto-run** — only on explicit user request; write to a file, report the path | `issue_supervisor_kubeconfig`, `issue_tkc_kubeconfig` |
| **L3** | Single write — user must approve | Authorized request; MCP preview gates and CLI confirmation are separate (see Notes) | `create_namespace`, `update_namespace`, `delete_namespace`, `create_tkc_cluster`, `upgrade_tkc_cluster`, `scale_tkc_cluster`, `delete_tkc_cluster` |
| **L4** | Multi-step plan / apply workflow | Plan generation auto; apply gated by user approval | *(roadmap — TKC fleet upgrades, multi-namespace bootstrapping plans)* |
| **L5** |

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/capabilities.md (reported line 13)May include surrounding context.

md
rvisor_status`, `list_supervisor_storage_policies`, `list_namespaces`, `get_namespace`, TKC list/get, `get_harbor_info`, `list_namespace_storage_usage` |
| **L2** | Read + analysis / recommendation | Always auto-run | namespace quota analysis, TKC health correlation, storage policy compatibility checks |
| **Credential** | Returns live access material (bearer token) | **Never auto-run** — only on explicit user request; write to a file, report the path | `issue_supervisor_kubeconfig`, `issue_tkc_kubeconfig` |
| **L3** | Single write — user must approve | Authorized request; MCP preview gates and CLI confirmation are separate (see Notes) | `create_namespace`, `update_namespace`, `delete_namespace`, `create_tkc_cluster`, `upgrade_tkc_cluster`, `scale_tkc_cluster`, `delete_tkc_cluster` |
| **L4** | Multi-step plan / apply workflow | Plan generation auto; apply gated by user approval | *(roadmap — TKC fleet upgrades, multi-namespace bootstrapping plans)* |
| **L5** | Auto-remediation from l

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/capabilities.md (reported line 105)May include surrounding context.

md
variable conversion, class rebase or upgrade clearance is provided.

This is an API/schema adaptation, **not end-to-end VKS/VCF 9.1 lab validation**.
Issue [#27](https://github.com/vmware-skills/VMware-VKS/issues/27)'s guest kubeconfig
401 remains a separate access-validation concern.

Sources: [Broadcom VKS API](https://developer.broadcom.com/xapis/vmware-vsphere-kubernetes-service/latest/api-docs.html),

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/capabilities.md (reported line 138)May include surrounding context.

md
ss-info [--tool NAME] [--target T]`.
- **Root folder only.** `not_granted_at_root` is not "no access": the privilege may be granted on a specific cluster. `undetermined` means vCenter did not answer; it is never read as granted.
- **What it cannot see.** This skill works through the vSphere Automation REST API and the Supervisor Kubernetes API, not SOAP. The per-tool table (`vmware_vks/access_requirements.py`) lists System.Read for inventory reads and StorageProfile.View for storage policies. Namespace create/update/delete also need Namespaces.Configure (per Broadcom's Automation API reference; not yet verified against a live vCenter's privilege list). TKC, VM Service, storage-usage and kubeconfig calls are authorized by the namespace's view/edit/owner permission, which a root-folder privilege check cannot answer, so those tools always report `undetermined` — never `granted`.
- **Typical response**: ~150 tokens for one tool; ~500 tokens for the whole-server summary.

## Safety Features

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/capabilities.md (reported line 161)May include surrounding context.

md
| vSphere Version | TKC API | Support |
|----------------|---------|---------|
| 8.0 / 8.0U1-U3 | `cluster.x-k8s.io/v1beta1` (ClusterClass) | Full |
| 9.0 / 9.1 (VCF 9) | Discovers served `v1beta1` or `v1beta2`; explicit class and admission required for modern creation | ⚠ Partial external 9.1 report — Supervisor login works at the Supervisor endpoint, but the guest TKC API rejected this skill's kubeconfig with 401 ([#27](https://github.com/vmware-skills/VMware-VKS/issues/27)). Maintainers have not verified the full API surface; check guest access separately. |
| 7.0 U3 | `run.tanzu.vmware.com/v1alpha3` | Not supported |
| 7.0 U1-U2 | `run.tanzu.vmware.com/v1alpha1` | Not supported |

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/cli-reference.md (reported line 108)May include surrounding context.

[-o ] [--target ]

text

Both commands are **credential access**: the kubeconfig embeds a Supervisor
bearer token (JWT from `/wcp/login`) that acts as your vCenter account until it
expires (typically hours). Run them only when the user asked for a kubeconfig,
and pass `-o`: the file is created owner-only (0600), also when it replaces an

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/cli-reference.md (reported line 110)May include surrounding context.

md
Both commands are **credential access**: the kubeconfig embeds a Supervisor
bearer token (JWT from `/wcp/login`) that acts as your vCenter account until it
expires (typically hours). Run them only when the user asked for a kubeconfig,
and pass `-o`: the file is created owner-only (0600), also when it replaces an
existing file, and a symlink target is refused. Both are `@guarded`, so the
retrieval is recorded in `~/.vmware/audit.db` (the token is not). Delete the