The metadata request is part of the configured S3 storage credential flow, and the shell-command finding is a scanner rule rather than an executed command. The reviewed findings do not establish unauthorized collection or other malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The flagged metadata access occurs when configured S3 storage needs role credentials; the shell pattern is checked by the workspace scanner.
Impact
No unauthorized credential transfer, install-time collection, or other malicious behavior was established.
Mechanism
The metadata code reads credentials from the AWS container credential endpoint for S3 use. The scan and Unicode findings are detection and text-cleaning logic.