Execution: Added Malicious Binary Executed

This document describes a threat finding type in Security Command Center. Threat findings are generated by threat detectors when they detect a potential threat in your cloud resources. For a full list of available threat findings, see Threat findings index.

Overview

A malicious binary that was not part of the original container image was executed. Attackers commonly install exploitation tooling and malware after the initial compromise.

Detection service

Cloud Run Threat Detection

How to respond

To respond to this finding, do the following:

Review finding details

1. Open the Execution: Added Malicious Binary Executed finding as directed in Reviewing findings. Review the details on the Summary and JSON tabs.

2. On the Summary tab, review the information in the following sections:

   • What was detected, especially the following fields:
     • Program binary: the absolute path of the added binary
     • Arguments: the arguments provided when invoking the added binary
     • Containers: the name of the affected container
     • Containers URI: the name of the container image being deployed
   • Affected resource, especially the following fields:
     • Resource full name: the full resource name of the affected Cloud Run resource
   • Related links, especially the following fields:
     • VirusTotal indicator: link to the VirusTotal analysis page

3. Identify other findings that occurred at a similar time for the affected container. Related findings might indicate that this activity was malicious, instead of a failure to follow best practices.

4. Review the settings of the affected container.

5. Check the logs for the affected container.

Research attack and response methods

1. Review MITRE ATT&CK framework entries for this finding type: Ingress Tool Transfer, Native API.
2. Check the SHA-256 hash value for the binary flagged as malicious on VirusTotal by clicking the link in VirusTotal indicator. VirusTotal is an Alphabet-owned service that provides context on potentially malicious files, URLs, domains, and IP addresses.
3. To develop a response plan, combine your investigation results with the MITRE research and VirusTotal analysis.

Implement your response

For response recommendations, see Respond to Cloud Run threat findings.

What's next

• Learn how to work with threat findings in Security Command Center.
• Refer to the Threat findings index.
• Learn how to review a finding through the Google Cloud console.
• Learn about the services that generate threat findings.