Back to skill

Security audit

issue-hunter

Security checks for vulnerabilities and agentic risk

Overview

This issue-triage skill is coherent and read-oriented, but users should handle GitHub tokens carefully.

Use the GitHub CLI's normal secure login flow when possible. If you use a token, make it fine-grained and read-only for the repositories being analyzed, keep it out of chats and project files, and redact it from any logs or shared 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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill explicitly tells the user to provide a GitHub token and suggests exporting it directly as an environment variable, but it does not warn that this credential is sensitive, should be scoped minimally, and must not be pasted into chats, logs, or generated artifacts. In an agent-assisted workflow, this increases the chance of credential exposure through terminal history, prompts, transcripts, or accidental file output, which could allow unauthorized access to GitHub resources under that token.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.