Back to skill

Security audit

Git Commit Range Summary

Security checks for vulnerabilities and agentic risk

Overview

The scanners flag a requirement to archive repository summaries in a GitHub-synchronized location, which is outside the stated summary-generation purpose; the verdict is suspicious, with medium confidence.

Review whether the synchronized archive destination is appropriate for your repository and whether you want summaries stored there before installing. The scan was partial: it inspected both listed components but could not resolve a referenced path, so the evidence is incomplete.

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
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • 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
Findings (1)

The skill mandates archiving repository-derived summaries in a GitHub-synchronized location, beyond its stated diff-analysis and summary-generation purpose.

Medium
Category
Excessive Agency
Confidence
91% confidence
Finding

The skill unconditionally saves repository-derived summaries to a directory explicitly described as GitHub-synchronized, without asking whether the user authorizes publication or whether that destination is appropriate for the repository's confidentiality. Summaries may disclose proprietary implementation details, security weaknesses, or internal PRD context to unintended readers if synchronization occurs; however, the supplied file does not itself execute a push or establish that the destination is public.

Content

No source excerpt is available for this finding.