T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:22- Finding
Unrestricted workspace aggregation may expose sensitive data to external messaging platforms
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is openly a fleet-monitoring coordinator, but it asks for broad workspace reads, external message delivery, optional credential copying, and optional cron retriggering that users should review carefully.
Install only if you are comfortable with a coordinator reading the specific workspaces you configure and sending summarized content to external chat platforms. Use dedicated scoped credentials, do not copy another agent's auth profile, exclude secrets and sensitive workspaces, use private messaging destinations, and leave self-healing disabled unless each retriggerable cron job is idempotent and approved.
SKILL.md:22Unrestricted workspace aggregation may expose sensitive data to external messaging platforms
SKILL.md:85Authentication profiles can be copied from a more privileged agent
SKILL.md:44Self-healing functionality can retrigger scheduled jobs without an enforceable safety boundary
SKILL.md:52Installation command retrieves an unpinned third-party package
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.
- **Workspace access:** The coordinator scans every workspace you configure. Restrict the workspace list to only what needs monitoring. Exclude any workspace containing credentials, secrets, or sensitive data.
- **Outbound messaging:** Briefing content is sent to Telegram (always) and optionally Discord/Slack. Review what gets included in the output format before enabling delivery to external platforms.
- **Auth scoping:** Use dedicated, scoped API credentials for the coordinator agent. Do not reuse auth profiles from other agents. The coordinator only needs read access to workspaces and write access to configured messaging channels.
- **Self-healing:** Automatically retriggering missed cron jobs can cause duplicate execution. Only enable this if your cron jobs are idempotent (safe to run twice). Disable self-healing by removing the retrigger rule from your SOUL.md if jobs have side effects.
## How It Works
No suspicious patterns detected.