The routed findings resolve to scanner patterns, documented examples, expected agent runtime capabilities, and credential use gated by explicit S3 configuration. No malicious or suspicious automatic behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
S3 storage must be configured with FOLDRUN_S3_ENDPOINT and FOLDRUN_S3_BUCKET; container credentials are fetched when role credentials are needed.
Impact
Expected authenticated object storage access; no unrelated credential transfer or install-time data collection was identified.
Mechanism
The driver reads credentials from the configured AWS container credential endpoint, then signs requests to the configured S3 endpoint.
Evidence
src/storage.tsconfigured S3 object keys
Network endpoints3
169.254.170.2${relative}AWS_CONTAINER_CREDENTIALS_FULL_URI (environment-configured)FOLDRUN_S3_ENDPOINT (environment-configured)