pilot-s3-bridge
Fail
Audited by Gen Agent Trust Hub on Jun 26, 2026
Risk Level: HIGHCOMMAND_EXECUTIONCREDENTIALS_UNSAFEDATA_EXFILTRATIONPROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The 'Workflow Example' script in
SKILL.mdcontains a critical command injection vulnerability. It processes external JSON requests from a network-connected listener (pilotctl recv) and interpolates fields like$BUCKET,$KEY, and$ACTIONdirectly into shell commands (aws s3 cp,aws s3 ls) without any sanitization or validation. An attacker could use backticks or subshell syntax in these fields to execute arbitrary code on the host. - Ingestion points: Data enters through
pilotctl --json recvon port 1008. - Sanitization: None. The script uses raw
jqoutput in string interpolation for shell execution. - Capability inventory: The script has the ability to execute
aws s3commands andpilotctlmessaging, and it runs a public daemon. - [CREDENTIALS_UNSAFE]: The documentation instructs users to hardcode highly sensitive credentials (
AWS_ACCESS_KEY_IDandAWS_SECRET_ACCESS_KEY) directly into the bridge script. This practice, combined with the command execution vulnerability, significantly increases the risk of credential theft. - [DATA_EXFILTRATION]: The lack of input validation allows for exfiltration of the hardcoded credentials and other environment variables. An attacker can manipulate the
pilotctl send-messageoraws s3commands to send sensitive data to an external location. - [PROMPT_INJECTION]: There is a discrepancy in author metadata;
README.mdidentifies the author asTeoSlayer, whileSKILL.mdidentifies the author asvulture-labs. This inconsistency in attribution can be misleading regarding the skill's origin and security responsibility.
Recommendations
- AI detected serious security threats
Audit Metadata