Back to skill

Security audit

License

Security checks for vulnerabilities and agentic risk

Overview

This is a simple local reference skill that prints static license-related documentation and shows no evidence of credential access, network use, persistence, or hidden behavior.

This skill appears safe to install as a static reference helper. Be aware that its documentation is generic and its subcommand names are broad, so invoke it explicitly as a license reference tool when you want this output.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · scripts/script.sh (reported line 64)May include surrounding context.

sh
## Prerequisites
- Basic understanding of devtools concepts
- Required tools and access credentials
- System meeting minimum requirements

## Installation

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The command triggers are common English terms like 'intro', 'security', 'patterns', and 'debugging', which are broad enough to collide with normal user conversation or unrelated requests. In an agent environment, underspecified triggers can cause accidental invocation of this skill, leading to context hijacking or unintended substitution of generic reference output for the user's actual task.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.