The manifest has no install hook, and the flagged child process is launched as the configured local gateway. AWS role proof and workload-token requests go to STS and the configured gateway for the SDK's runtime features; the reviewed source shows no unrelated collection or exfiltration.
Static reason
One or more suspicious static signals were detected.
Trigger
Runtime startup with gateway identity or a configured local gateway; AI binding occurs when the runtime prepares an enabled AI connection.
Impact
No evidence of credential theft, unrelated data collection, or concealed execution.
Mechanism
The runtime proves its AWS role to STS using a presigned GetCallerIdentity URL, sends that proof to the configured gateway, and uses a workload token for the gateway's AI connection endpoint. The local gateway process uses the configured binary and config file.
Network endpoints3
sts.<region>.api.aws<configured gatewayUrl>/_harbour/internal/session<configured gatewayUrl>/_harbour/internal/ai/connection