Back to skill

Security audit

Regex Patterns

Security checks for vulnerabilities and agentic risk

Overview

This is a regex reference skill with no bundled executable code, and its risky examples are visible command-line snippets rather than hidden behavior.

Before using the refactoring snippets, preview matches first, keep changes under version control, and scope commands to the intended files. Treat the validation regexes as examples rather than universal correctness guarantees.

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

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill documents multiple in-place editing commands such as sed -i and bulk replacements piped through xargs, which can irreversibly modify many files if copied blindly. In the context of an agent skill intended for practical command reuse, the absence of warnings, dry-run alternatives, or backup guidance increases the chance of accidental codebase corruption or unintended mass edits.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
85% confidence
Finding

The documentation includes a dedicated 'US phone' regex example, which privileges a specific locale without stating that it is only one regional example or providing guidance for other locales. Under the policy, locale-specific behavior should either be optional, clearly scoped, or accompanied by user choice.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.