Back to skill

Security audit

ISSUE Triage

Security checks for vulnerabilities and agentic risk

Overview

This skill helps triage pasted GitHub issue text and does not request network access, credentials, persistence, or code execution.

This appears safe to install for triaging GitHub issue text. Users should avoid pasting secrets, private tokens, or sensitive customer data into issue reports because the skill will analyze whatever text they provide.

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
  • 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 (4)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The manifest says to trigger when the user asks to 'triage an issue', 'analyze a bug report', or asks 'how should I respond to this issue'. These phrases are broad natural-language requests without clear scope constraints or negative examples, which could cause unintended invocation outside the intended GitHub issue triage context.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · SKILL.md (reported line 21)May include surrounding context.

md
1. **Gather Information:**
   - The user MUST provide the **raw issue text** or **markdown content** in their prompt.
   - **Do NOT** attempt to fetch issue content via `curl`, `gh api`, or by accessing external URLs (e.g., `https://github.com/...` or `https://api.github.com/...`). Fetching external, untrusted content at runtime poses a security risk (indirect prompt injection) and is strictly prohibited.
   - If the user only provides a URL, politely ask them to copy and paste the issue content directly into the chat.

2. **Analyze the Issue:**

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

The first expected output explicitly requires 'A Chinese Triage Report' while the second requires 'An English Triage Report'. This introduces language-specific behavior in natural-language requirements, but the file does not state that language is user-selected or otherwise policy-justified.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
76% confidence
Finding

This is a manifest-style JSON file, so vague-trigger review applies. The examples show generic issue-triage requests such as '帮我看看这个 Issue' and 'Triage this issue' without any documented limits, negative examples, or activation boundaries, which could overlap with common support phrasing and make invocation scope unclear.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.