T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:164- Finding
Explicit Sandbox Bypass Through Host-Accessible Scheduled Command Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill needs Review because it tells agents to share API keys with autonomous sessions and schedule recurring host-level commands to work around sandbox limits without enough guardrails.
Install only if you trust the external fleet tools and will use this in a controlled environment. Treat injected provider keys as exposed to every recipient session, use short-lived scoped credentials, avoid PROXY_URL or CUSTOM_* unless reviewed, and do not schedule host-side cron commands without explicit human approval, fixed allowlisted jobs, logging, expiration, and a removal path.
SKILL.md:164Explicit Sandbox Bypass Through Host-Accessible Scheduled Command Execution
SKILL.md:105Broad API Credential and Proxy Configuration Injection into Autonomous Sessions
The skill explicitly instructs operators to inject provider API keys into spawned or filtered autonomous sessions, but it does not prominently warn that any code or agent logic running in those sessions may access and exfiltrate those secrets. In this context, the capability materially expands secret exposure from the trusted main process to additional semi-autonomous execution contexts, making misuse or compromise more likely.
The documentation recommends scheduling commands on the host-accessible main session specifically to bypass sandbox cron restrictions, but it does not clearly warn that these scheduled commands execute outside container isolation and may affect the host environment persistently. Even with a character allowlist, running scheduled commands on the main session increases the blast radius to host files, processes, network access, and repeated execution over time.
No suspicious patterns detected.