T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:32- Finding
Unbounded System and Process Reconnaissance
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a plausible maintenance-audit skill, but it asks an agent to inspect sensitive operational data too broadly and permits limited code changes without a clear approval gate.
Install only if you are comfortable giving the agent a narrowly scoped maintenance-audit role. Before running it, specify exact directories, scheduled jobs, accounts, and memory files in scope; prohibit reading or storing secret values; require redaction in reports; and require explicit approval for every code or cleanup change.
SKILL.md:32Unbounded System and Process Reconnaissance
SKILL.md:52Unsafe Discovery and Reporting of API Credential Inventory
SKILL.md:61Unbounded Inspection of Installed Skills and Persistent Agent Context
SKILL.md:132Unauthorized Source Modification Through Cleanup Exception
The manual trigger condition is broad enough that ordinary user complaints like unexpected bills or degraded reliability could invoke a high-scope audit over crons, scripts, API keys, memories, and subscriptions without clear confirmation boundaries. In an agent environment, ambiguous invocation increases the chance of unintended reconnaissance across sensitive operational data and can lead to risky follow-on recommendations or edits.
The listed trigger phrases are common conversational requests that could easily appear in normal dialogue, causing accidental activation of a privileged maintenance workflow. Because this skill inspects scheduled tasks, scripts, keys, memory files, and tools, accidental invocation expands access to sensitive metadata and increases the chance of unintended state changes later in the workflow.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
### 1. Crons — Are they alive and earning their keep?
For each launchd agent / cron job / scheduled task:
- Is the process actually running? (check PID, plist/cron status)
- When did it last fire successfully?
- What does it produce? Is that output being consumed by anything?
- Is there a newer/better approach that renders this obsolete?