Back to skill

Security audit

Trace

Security checks for vulnerabilities and agentic risk

Overview

This skill is a simple local reference-doc command with no evidence of credential access, network activity, persistence, or destructive behavior.

This appears safe to install as a static reference helper. Be aware that the content is generic and the short topic names should be used through the trace command, not treated as standalone agent instructions.

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
87% confidence
Finding

The manifest/markdown describes the skill simply as "trace" and lists generic commands like "intro" and "security" without specifying how the skill is invoked, what context activates it, or any exclusion conditions. These short, common terms are ambiguous enough that they could overlap with ordinary conversation or other command namespaces, increasing the risk of unintended invocation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.