ClawHub
Back to skill

Security audit

vx-usage

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed vx usage guide with some supply-chain and credential-handling caveats, but no hidden execution, exfiltration, or destructive behavior in the artifact.

Before installing, treat this as guidance for vx-managed projects, not a reason to route every Git or GitHub task through vx. Pin MCP packages, GitHub Actions refs, and container tags for production use, and keep tokens in secret stores or environment injection rather than tracked config.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (5)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill advertises activation on very broad triggers such as general Git/GitHub operations and cross-platform setup, which can cause it to be injected into unrelated tasks. Over-broad activation increases the chance that agents follow repository-specific operational guidance in the wrong context, potentially leading to inappropriate command usage, unnecessary external access, or policy bleed between tasks.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
70% confidence
Finding

npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
91% confidence
Finding

The MCP example includes GITHUB_TOKEN usage without any accompanying credential-handling guidance. In practice, this can normalize placing sensitive tokens directly into configs, prompts, logs, or shared files, increasing the likelihood of accidental secret exposure by agents or users.

Content

No source excerpt is available for this finding.