1. Resources
  2. Detection rules
  3. Primary Admin or Secondary Email Changed in Google Workspace

Primary Admin or Secondary Email Changed in Google Workspace detection rules

An attacker with domain settings rights changes the primary admin or the secondary email of a Google Workspace account, so that Google's critical notices, billing messages and support mail go to an address they read.

Platform
Google Cloud
Severity
Medium
Log source
Google Cloud Audit Logs
Last updated
MITRE ATT&CK technique
T1098Account Manipulation
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
An admin account with the Domain settings privilege, or a super admin account, and for the primary admin field a super admin account to name.
Impact
Google's critical notifications, billing messages and support communication for the account reach the attacker instead of the owners.
Response
Restore the recorded primary admin and secondary email, check what Google sent in the meantime and secure the admin account that made the change.
Mitigation
Limit the Domain settings privilege, record both contact fields and forward Google's notifications to a monitored group of administrators.
API methods
google.admin.AdminService.updateDomainSecondaryEmailgoogle.admin.AdminService.updateDomainPrimaryAdminEmail

How the attack works

Every Google Workspace and Cloud Identity account has contact details in its profile. The primary admin is the one super admin account that receives Google's critical alerts and notifications. Google lists what is sent there, including changes to the services, billing notifications and communications from Support. The secondary email is another address for the same messages, and Google requires it to be outside the organization's domain. Both are set under Account settings, Profile, Contact info, and Google states that this page requires the Domain settings privilege.

An attacker who holds that privilege can point both fields at accounts they control. From then on the real owners no longer see what Google sends about the account, and the attacker does. That covers warnings about the account, billing notices and the answers of Google Support. The secondary email is by design an outside mailbox, for example a personal Gmail address, which the organization cannot monitor. The change does not grant an admin role, which is why it is easy to overlook.

The Admin audit log records UPDATE_DOMAIN_PRIMARY_ADMIN_EMAIL and UPDATE_DOMAIN_SECONDARY_EMAIL, each with the domain and the old and the new address. Organizations that share Workspace data with Google Cloud receive them in Cloud Audit Logs at organization level as Admin Activity entries of admin.googleapis.com. Google's alert center has an alert type for a changed primary admin as well.

What an attacker needs

  • An admin account with the Domain settings privilege, or a super admin account.
  • For the primary admin field, a super admin account to name. Google states that the field takes the username of a super admin.

Impact

Google's critical notifications, billing messages and support communication for the account reach the attacker instead of the owners. Warnings go unseen, and the attacker holds the mailbox that Google writes to about the account. The change gives no administrative access by itself.

Detection rules

Account Secondary Email Changed in Google Workspace

Detects a change of the secondary email of a Google Workspace or Cloud Identity account (Admin audit event UPDATE_DOMAIN_SECONDARY_EMAIL, rendered as "Secondary email for your organization changed from {OLD_VALUE} to {NEW_VALUE}"). The secondary email is a contact address of the whole account, not of one user. Google requires it to be outside the organization's domain and sends important account messages to it, so whoever owns the new mailbox receives them and the organization cannot monitor it. The previous and the new address are the parameters OLD_VALUE and NEW_VALUE in protoPayload.metadata and the admin who made the change is in principalEmail. The entry reaches Cloud Audit Logs as an Admin Activity entry at organization level, which is always written once Google Workspace data sharing with Google Cloud is enabled, and reaches the SIEM only when the organization-level logs are routed to it.

LevelMediumStatusExperimentalLog sourceGoogle Cloud Audit Logs
title: Account Secondary Email Changed in Google Workspace
id: 82b0903b-eafa-4cc4-98ef-5fc8f5a5290b
status: experimental
description: >-
  Detects a change of the secondary email of a Google Workspace or Cloud
  Identity account (Admin audit event UPDATE_DOMAIN_SECONDARY_EMAIL,
  rendered as "Secondary email for your organization changed from
  {OLD_VALUE} to {NEW_VALUE}"). The secondary email is a contact address
  of the whole account, not of one user. Google requires it to be outside
  the organization's domain and sends important account messages to it, so
  whoever owns the new mailbox receives them and the organization cannot
  monitor it. The previous and the new address are the parameters OLD_VALUE
  and NEW_VALUE in protoPayload.metadata and the admin who made the change
  is in principalEmail. The entry reaches Cloud Audit Logs as an Admin
  Activity entry at organization level, which is always written once Google
  Workspace data sharing with Google Cloud is enabled, and reaches the SIEM
  only when the organization-level logs are routed to it.
references:
  - https://docs.cloud.google.com/logging/docs/audit/gsuite-audit-logging
  - https://developers.google.com/workspace/admin/reports/v1/appendix/activity/admin-domain-settings
  - https://knowledge.workspace.google.com/admin/getting-started/ensure-you-receive-critical-notifications-and-updates-for-your-google-workspace-account
  - https://attack.mitre.org/techniques/T1098/
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.t1098
logsource:
  product: gcp
  service: gcp.audit
detection:
  selection:
    protoPayload.serviceName: admin.googleapis.com
    protoPayload.methodName: google.admin.AdminService.updateDomainSecondaryEmail
  condition: selection
falsepositives:
  - An administrator who replaces the address of a former owner or of a previous service provider. The field changes very rarely, so verify every event and confirm who owns the new mailbox.
level: medium

False positives

  • An administrator who replaces the address of a former owner or of a previous service provider. The field changes very rarely, so verify every event and confirm who owns the new mailbox.

Primary Admin Changed in Google Workspace

Detects a change of the primary admin of a Google Workspace or Cloud Identity account (Admin audit event UPDATE_DOMAIN_PRIMARY_ADMIN_EMAIL, rendered as "Primary admin for your organization changed from {OLD_VALUE} to {NEW_VALUE}"). The primary admin is the one super admin account that receives Google's critical alerts, billing notifications and communications from Support, so a change redirects those messages. The previous and the new address are the parameters OLD_VALUE and NEW_VALUE in protoPayload.metadata and the admin who made the change is in principalEmail. The field does not grant a role. The entry reaches Cloud Audit Logs as an Admin Activity entry at organization level, which is always written once Google Workspace data sharing with Google Cloud is enabled, and reaches the SIEM only when the organization-level logs are routed to it.

LevelMediumStatusExperimentalLog sourceGoogle Cloud Audit Logs
title: Primary Admin Changed in Google Workspace
id: 2022426e-0085-4b07-8984-e6d34519701f
status: experimental
description: >-
  Detects a change of the primary admin of a Google Workspace or Cloud
  Identity account (Admin audit event UPDATE_DOMAIN_PRIMARY_ADMIN_EMAIL,
  rendered as "Primary admin for your organization changed from
  {OLD_VALUE} to {NEW_VALUE}"). The primary admin is the one super admin
  account that receives Google's critical alerts, billing notifications
  and communications from Support, so a change redirects those messages.
  The previous and the new address are the parameters OLD_VALUE and
  NEW_VALUE in protoPayload.metadata and the admin who made the change is
  in principalEmail. The field does not grant a role. The entry reaches
  Cloud Audit Logs as an Admin Activity entry at organization level, which
  is always written once Google Workspace data sharing with Google Cloud is
  enabled, and reaches the SIEM only when the organization-level logs are
  routed to it.
references:
  - https://docs.cloud.google.com/logging/docs/audit/gsuite-audit-logging
  - https://developers.google.com/workspace/admin/reports/v1/appendix/activity/admin-domain-settings
  - https://knowledge.workspace.google.com/admin/getting-started/ensure-you-receive-critical-notifications-and-updates-for-your-google-workspace-account
  - https://attack.mitre.org/techniques/T1098/
author: Forestall
date: 2026-11-18
tags:
  - attack.persistence
  - attack.t1098
logsource:
  product: gcp
  service: gcp.audit
detection:
  selection:
    protoPayload.serviceName: admin.googleapis.com
    protoPayload.methodName: google.admin.AdminService.updateDomainPrimaryAdminEmail
  condition: selection
falsepositives:
  - The person who signed up for the service leaves or hands the account over, and another super admin becomes the primary admin. The field changes very rarely, so verify every event with the super admins.
level: medium

False positives

  • The person who signed up for the service leaves or hands the account over, and another super admin becomes the primary admin. The field changes very rarely, so verify every event with the super admins.

Triage

  • Read OLD_VALUE and NEW_VALUE in the event parameters in protoPayload.metadata for the previous and the new address, and DOMAIN_NAME for the domain.
  • For the secondary email, find out who owns the new outside address. An address nobody in the administration team recognizes is the finding.
  • For the primary admin, check when the named account became a super admin and who assigned the role.
  • Identify the admin who made the change (principalEmail), confirm it with that person through a second channel and check the recent sign-ins of that account.
  • Look for other changes by the same admin around that time, such as admin roles, recovery settings and reseller access.

Response

Once the attack is confirmed:

  1. Set the primary admin and the secondary email back to the recorded values.
  2. Check the messages Google sent while the fields were changed. Review billing, the Admin console notifications and open support cases, and tell Google Support if a case was opened or answered by someone else.
  3. Secure the admin account that made the change. Reset its password, reset its sign-in cookies and review its 2-Step Verification methods and admin roles.
  4. If the new primary admin is an account you do not recognize, treat it as an unauthorized super admin. Suspend it and review everything it did.
  5. Review what else the same admin changed in the period.

Mitigation

  • Give the Domain settings privilege only to the administrators who manage the account profile, and keep super admins few.
  • Use a monitored mailbox for the primary admin and forward Google's notifications to a group of administrators with a mail filter, as Google's help page describes.
  • Record the primary admin and the secondary email of the account and compare the profile with the record regularly.
  • Send the alert center alert for a changed primary admin to the security team.
  • Share Workspace data with Google Cloud and route the organization-level audit logs to the SIEM.

Frequently asked questions

What does the primary admin of a Google Workspace account receive?

Google states that it periodically sends critical alerts and notifications to the primary administrator account and that only one super admin account receives them. The messages it lists are feature availability, functionality changes, billing notifications, changes to the Google Workspace or Cloud Identity services and communications from Support. Initially the person who signed up for the service is the primary admin.

Does changing the primary admin make someone a super admin?

No. The field does not grant a role. Google states that it takes the username of a super admin, so the named account has to hold the role already. If the new primary admin is unfamiliar, look for the earlier event in which that account received the Super Admin role.

Why is a changed secondary email a security concern?

Google requires the secondary email to be outside the domain used for the Google service, and gives a personal Gmail address as an example. Messages about the account are sent there as well. The organization cannot monitor or recover a mailbox outside its domain, so an attacker who sets it keeps receiving those messages after the admin account they used has been secured.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.