Skills/ClawHub/vmware-nsx-security

vmware-nsx-security@1.17.4

CAUTION· static only

Publisher claims: "Use this skill whenever the user needs to manage VMware NSX security (rebranded VMware vDefend in VCF 9) — distributed firewall (DFW) policies, security groups, microsegmentation, and IDS/IPS. Directly handles: create/manage DFW policies and rules, security groups, VM tags, network traceflow diagnostics, IDPS profiles and status. Always use this skill for "create firewall rule", "set up microsegmentation", "add VM to security group", "run traceflow", "check IDS status", "vDefend firewall rule", or any NSX security / vDefend / DFW task. Do NOT use for NSX networking operations like segments, gateways, NAT, or routing (use vmware-nsx), or VM lifecycle (use vmware-aiops). For load balancing/AVI/AKO use vmware-avi." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher zw008 · publishing for 186 daysInstalls 5,666Last detonated 1 h ago

Coverage

Static only; nothing was run yet.

The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.

What changed since 1.17.2

vet-skills diff vmware-nsx-security 1.17.2 1.17.4

In the sandbox, this version reached for nothing 1.17.2 did not. Compared from the two recorded runs, not from source.

1.17.4 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-19 and scored it 57/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Persistence: instructs the agent to auto-load this skill in future sessions; Access to sensitive file paths; Access to sensitive file paths. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

HIGH
Persistence: instructs the agent to auto-load this skill in future sessionsSKILL.md:6 · Persistence: instructs the agent to auto-load this skill in future sessions…ity groups, VM tags, network traceflow diagnostics, IDPS profiles and status. Always use this skill for "create firewall rule", "set up microsegmentation", "add VM to security gro…Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathsSKILL.md:17 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files…Manager target requires a per-target password env var in ~/.vmware-nsx-security/.env following the pattern VMWARE_NSX_SECURITY_<TARGET_NAME_UPPER>_PASSWORD. Passwor…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:304 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- **Credential safety**: Passwords loaded only from environment variables (`.env` file), never from `config.yaml`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:316 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Add to ~/.vmware-nsx-security/.env (create if missing, chmod 600):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:53 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesvmware-nsx-security init # guided setup: writes config + .env (chmod 600, password grep-safe), then verifiesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Collapsed <details> block carrying instructionsreferences/detailed-guide.md:122 · Collapsed <details> block carrying instructions<summary>Preinstalled CLI and additional MCP options</summary> ### MCP Server Setup **After `uv tool install vmware-nsx-security==1.17.4`, start the MCP server Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathsSKILL.md:288 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files`VMWARE_NSX_SECURITY_NSX_PROD_PASSWORD`. Check `~/.vmware-nsx-security/.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File permission modification commandSKILL.md:316 · File permission modification command — agent changes file ownership/permissions# Add to ~/.vmware-nsx-security/.env (create if missing, chmod 600):Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File permission modification commandSKILL.md:53 · File permission modification command — agent changes file ownership/permissionsvmware-nsx-security init # guided setup: writes config + .env (chmod 600, password grep-safe), then verifiesFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
File permission modification commandSKILL.md:318 · File permission modification command — agent changes file ownership/permissionschmod 600 ~/.vmware-nsx-security/.envFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈5,335 tok
1 file · 11 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.

What would make this Verified

23 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim zw008: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
  3. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  4. File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim zw008Propose a patch to the maintainer