Vext Shield

• Risk level: Low
• Analyzed: Mar 5, 2026, 1:01 AM
• Findings: 0
• Version: 1.2.0

Overview

The skill is internally coherent with its stated purpose (an on-host security scanner / red team suite); the dangerous strings and payloads are test data and signatures used for detection, not unexplained exfiltration requests — but you should only install it if you trust the publisher and can run its sandbox requirements.

This package is a self-contained on-host security suite that includes a static signature database and adversarial test payloads. The presence of many 'malicious' strings and test scripts is intentional — they are used to detect and validate detections. Before installing: 1) Verify you trust the publisher (Vext Labs) or inspect the source yourself; 2) Ensure your host can provide the required OS-level sandboxing tools (macOS: sandbox-exec; Linux: unshare) because the red-team and sandboxed behavioral tests refuse to run without them; 3) Expect local files to be created under ~/.openclaw/vext-shield/ (reports, logs, firewall-policy, baselines); 4) Review shared/threat_signatures.json and skills/vext-redteam/redteam.py if you want to confirm which payloads are included; 5) If you lack kernel sandboxing or are uncomfortable with adversarial test payloads on your machine, avoid running the red-team behavioral tests and restrict usage to static scan/audit functions. Finally, although the code claims 'zero network requests', you should still audit the code paths that parse decoded payloads and any code that would process user-provided inputs to ensure no accidental outbound network actions occur in your environment.