The metadata access is tied to explicitly configured S3 storage and AWS container credential settings. The apparent shell-pipeline finding is explanatory scanner text, and the inspected entry point and credential flow show no malicious behavior.
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`, and container credentials must be available.
Impact
No unintended credential collection or transmission was identified in the inspected flow.
Mechanism
Storage reads AWS container credentials from the AWS-configured endpoint and uses them to sign S3 requests.
Network endpoints1
169.254.170.2 (AWS container credential endpoint when the relative URI is configured)