T05 · Unauthorized Access and Privilege Escalation
Warning
- Location
SKILL.md:29- Finding
Broad Workspace Data Collection Without Prior Consent or Least-Privilege Scoping
- Content
View full analysis
' | sort -u git log --oneline -50 --all git log --since='30 days ago' --oneline --all | head -20 ``` ### 1b. Project structure ```bash ls -d */ 2>/dev/null cat *.yaml *.yml 2>/dev/null | head -50 ``` ### 1c. Tech stack signals Look for `package.json`, `requirements.txt`, `go.mod`, `Cargo.toml`, `pyproject.toml`, or similar. Read framework choices. ### 1d. Existing memory and feedback patterns Check for memory files or CLAUDE.md that reveal preferences. ### 1e. Content signals Check for blog posts, research docs, or README content that reveals interests. ``` The automatic behavior is also enabled for a first session at line 24 and reinforced by the instruction at line 110 to gather as much context as possible before asking questions. ### Technical Analysis The skill directs the agent to inspect data before asking the user for permission. Its collection scope includes: - Git author names and email addresses from every branch and reference through `git log --all`. - Recent repository activity and commit metadata. - The first 50 lines of every top-level YAML file. - Existing agent memory and instruction files. - Blog posts, research documents, and other content that may reveal personal interests. The command `cat *.yaml *.yml` is particularly overbroad. YAML files can contain deployment settings, access tokens, service credentials, internal hostnames, account identifiers, or other data unrelated to building a user profile. No exclusion list, secret detection, redaction process, source allowlist, or data-minimization requirement ...[truncated 1973 chars]- Remediation
View remediation