This is an SDK workload-attestation flow: metadata lookup occurs when workload-token authentication is used, and the resulting proof is sent to the Hikigai platform exchange endpoint. The AWS secret is used to sign the proof locally, and the source shows no unrelated collection or destination.
Static reason
One or more suspicious static signals were detected.
Trigger
A request using a Hikigai Deploy key needs a workload token; ordinary non-Deploy keys skip this exchange.
Impact
The platform receives workload identity proof and returns a short-lived token. The AWS secret access key is used locally for signing rather than included in the proof.
Mechanism
The SDK obtains configured ECS credentials or a GCP identity token, creates an identity proof, and sends it to the Hikigai platform auth exchange endpoint.
Network endpoints5
backend.hikigaiplatform.io/api/v1/auth/exchange169.254.170.2 (ECS relative credential endpoint)AWS_CONTAINER_CREDENTIALS_FULL_URI (configured endpoint)metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/identity