T05 · Unauthorized Access and Privilege Escalation
Warning
- Location
SKILL.md:14- Finding
Overbroad Git Command Permission Violates Least Privilege
- Content
View full analysis
- Remediation
View remediation
Security audit
golang-concurrency
Security checks for vulnerabilities and agentic risk
Overview
The skill is mostly a coherent Go concurrency helper, but it requests unrestricted Git command access that can change repository state beyond the stated need.
Install only if you are comfortable granting the agent broad repository editing and unrestricted Git authority. Prefer running it in a working tree without valuable uncommitted work or remote credentials, or narrow Git access to read-only commands unless a task explicitly needs mutation.
Vulnerability Patterns
- Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
- 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
Findings (1)
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 (2)
Intent-Code Divergence
Medium
- Category
- Not specified by scanner
- Confidence
- 96% confidence
- Finding
The comment on L296 asserts safety because each goroutine writes to its own index, but the closure directly captures loop variables i and url from the range loop. Unlike the earlier WaitGroup section, this example does not restate the Go 1.22+ loop-variable condition or make defensive copies, so the documentation's safety claim can be false in older modules and is internally inconsistent with the file's own earlier caution.
- Content
Intent-Code Divergence
Low
- Category
- Not specified by scanner
- Confidence
- 77% confidence
- Finding
The file earlier gives strong normative guidance to avoid holding synchronization primitives across blocking operations, yet the sync.Once example wraps sql.Open inside Once.Do without any caveat. While sync.Once is not a mutex, the surrounding guidance presents an intent of minimizing blocking inside synchronization, and the example appears to normalize potentially blocking one-time initialization under a sync primitive.
- Content
Static analysis
No suspicious patterns detected.