Suspicious Compute Instance Metadata Modification in GCP

PremiumReviewedSigma · Medium · v1
Product
gcp
Service
gcp.audit
Author
HuntRule
Published
2026-10-18
Updated
2026-10-18

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Cred Access

  4. Discovery

  5. Lateral Movement

  6. Collection

  7. C2

  8. Exfiltration

  9. Impact

What it detects

This rule detects modification of GCP compute instance metadata through compute.instances.setMetadata, a technique adversaries use to inject SSH keys or startup scripts and gain execution on virtual machines. Changing instance metadata via the control plane provides persistent access without touching the guest network. Detecting this call exposes credentialed access into compute workloads.

Related detections9 linkedT1078.004 — drag to rearrange
Suspicious SSH Key Push to EC2 via EC2 Instance Connect
Suspicious Okta Application Self-Assignment to All Applications by UNC3944 (via cloud)
Suspicious Google Cloud Function Create or Update Triggering Build
Malicious EKS Access Policy Association Granting Cluster Admin
Suspicious Azure AD Authentication Method Registration for Account Takeover (via azure)
Suspicious VM Run Command Execution in Azure
Malicious JavaGhost Security Group Creation (via cloudtrail)
Suspicious S3 Access from Desktop File Transfer Clients by Bling Libra
Suspicious Lambda Function Creation Across Regions in AWS Extortion Operation
Suspicious Compute Instance Metadata Modification in GCP
Pivot detection · T1078.004 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.