Back to skill

Security audit

Vitest Config Validator

Security checks for vulnerabilities and agentic risk

Overview

This skill is a local Vitest config checker that reads config files and reports issues without executing project code or making persistent changes.

Install only if you are comfortable with a local Python script reading the Vitest or Vite config files you pass to it. It does not appear to execute project code, change files, contact the network, or persist anything.

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
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

Tool Parameter Abuse

High
Category
Tool Misuse
Content
def strip_comments(text: str) -> str:
    """Remove // and /* */ comments outside of string literals, preserving line structure."""
    result = []
    i = 0
    n = len(text)
Confidence
90% confidence
Finding
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Lp3

Medium
Category
MCP Least Privilege
Confidence
90% confidence
Finding
The skill advertises commands that read arbitrary local files such as `vitest.config.ts`, but it does not declare any explicit tool scope, permissions, or allowed-tools boundary. In an agent environment, this can lead to over-broad file access because the runtime may permit file reads beyond the intended config files, increasing the chance of unintended data exposure.

Static analysis

No suspicious patterns detected.