logs-stop
Fail
Audited by Gen Agent Trust Hub on Sep 11, 2026
Risk Level: HIGHCOMMAND_EXECUTIONPRIVILEGE_ESCALATIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The skill instructs the agent to treat
$ARGUMENTSas a search term for log files when other specific filters are not used. The instructions lack guidance for the agent to sanitize or escape this input before interpolating it into shell commands likegrep, which can lead to command injection if a malicious search term is provided. - [COMMAND_EXECUTION]: The skill performs process termination using
killbased on PIDs retrieved from local marker files (e.g.,logs/.sim-capture.pid). While the skill includes a validation step usingpsto verify the command string associated with the PID before execution, the pattern of managing system processes based on file-derived input is a sensitive operation. - [PRIVILEGE_ESCALATION]: The instructions explicitly direct the agent to prompt the user to execute a local script using the platform's dynamic context syntax (
! ./scripts/collect_device_logs.sh) to facilitate interactivesudoaccess. This bypasses standard user interaction patterns in favor of high-privilege operations. - [INDIRECT_PROMPT_INJECTION]: The skill processes and summarizes untrusted data from log files (e.g.,
logs/sim-*.log,logs/device_*.txt). It lacks necessary security measures for this attack surface: - Ingestion points: Data is read from multiple log files created by background capture processes.
- Boundary markers: No delimiters or "ignore embedded instructions" warnings are utilized when presenting log content to the agent.
- Capability inventory: The skill possesses the ability to kill processes, remove files, and execute shell searches.
- Sanitization: There is no evidence of filtering or sanitizing the log content before it is processed by the agent, allowing potential malicious instructions embedded in logs to influence agent behavior.
Recommendations
- AI detected serious security threats
Audit Metadata