agent-squad
Fail
Audited by Gen Agent Trust Hub on Aug 11, 2026
Risk Level: HIGHCOMMAND_EXECUTIONPROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The Node.js script located at
scripts/agent-squadis vulnerable to command injection. In thestartHeartbeatsfunction, the script builds a shell command by interpolating the agent's name and role directly into a string executed viaexecSync. Because these inputs are not sanitized or escaped, a user or a malicious configuration could include shell metacharacters (e.g., semicolons, backticks, or pipes) in an agent's role to execute arbitrary code when the squad is started. - [COMMAND_EXECUTION]: The
editAgentfunction in the management script usesexecSyncto launch a system editor defined by theEDITORenvironment variable. While this is a common CLI pattern, the lack of validation on the file paths constructed from agent names could be exploited to manipulate the filesystem if agent names are crafted with path traversal or shell injection sequences. - [PROMPT_INJECTION]: The skill implements an 'indirect prompt injection' attack surface by design. The 'heartbeat' mechanism instructs agents to wake periodically and process content from external APIs (Linear, Trello, GitHub Issues). The instructions provided to the agents in
startHeartbeatslack boundary markers or explicit safety directives, meaning an attacker who can comment on a linked task or issue could potentially override agent behavior or trigger unintended tool usage. - [PROMPT_INJECTION]: The evidence chain for the indirect injection vulnerability includes:
- Ingestion points: External task systems (Linear, Trello, GitHub) via the
linear,trello, andgithubskills. - Boundary markers: Absent in the
heartbeatMsgconstruction. - Capability inventory: Agents have access to web search (
ddg), deep reading (web_fetch), file management (github), and inter-agent communication (sessions_send). - Sanitization: None observed in the orchestration logic.
Recommendations
- AI detected serious security threats
Audit Metadata