The scanner’s command-execution and credential-flow signals are consistent with an interactive CLI: its install scripts are absent, its API requests authenticate to the selected CodeFlow site, and client configuration writes are triggered by user selection. I found no automatic collection or forwarding of other providers’ credentials.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI; client configuration changes follow an explicit target selection.
Impact
No malicious impact identified. The expected effect is a local client configuration change.
Mechanism
The CLI authenticates to the default or configured CodeFlow site and writes the selected relay settings into local client configuration.
Evidence
Client configuration files selected by the user, including settings.json, config.toml, config.yaml, and .env
Network endpoints2
codeflow.sh (default)CODEFLOW_SITE (optional site override)